desktop_windows
warning Status
local_offer Category
close Clear
search Search
Features
19 features passed
62 features failed, 0 skipped
Scenarios
779 scenarios passed
439 scenarios failed, 0 skipped, 0 others
Steps
3,269 steps passed
783 steps failed, 667 skipped, 0 others
Timeline (seconds)
  • Validation on Account Information section for registered free user dashboard page Jul 4, 2025 04:13:18 PM Fail
    check_circle cancel clear
    00 02 04.768
    check_circle Scenario: Verify Weight should accept only Numeric Value
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User Edit Weight field with valid data
    • check_circleThen User should see that entered weight is displayed in Weight field
    00 01 53.193
    check_circle Scenario: Verify age should accept only Numeric Value
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User edit age field with valid data
    • check_circleThen User should see that entered age is displayed in that field
    00 01 34.935
    check_circle Scenario: Verify height should accept only Numeric Value
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User Edit height field with valid data
    • check_circleThen User should see that entered height is displayed in Height field
    00 03 20.359
    cancel Scenario: Verify Exercise Routine Level dropdown is displayed with options
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • cancelWhen User clicks the dropdown of Exercise Routine Level
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _E_x_e_r_c_i_s_e_ _R_o_u_t_i_n_e_ _L_e_v_e_l_ _d_r_o_p_d_o_w_n_ _i_s_ _d_i_s_p_l_a_y_e_d_ _w_i_t_h_ _o_p_t_i_o_n_s_
    00 07 14.310
    cancel Scenario: Verify Cuisine Preferences dropdown is displayed with options
    • check_circleGiven User is in Home Page after logged in
    • cancelAnd User is in Dashboard page
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 46.820
    check_circle Scenario: Verify Food Allergies dropdown is displayed with options
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User clicks the dropdown of Food Allergies
    • check_circleThen User should see the dropdown list of common allergy options "None","Dairy","Gluten","Shellfish","Soy","Eggs","Nuts","Other"
    00 03 00.939
    check_circle Scenario: Verify account details cannot be updated with invalid data
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User edit with invalid data and click save changes
    • check_circleThen User should see Error message
    00 00 30.883
    check_circle Scenario: Verify account details can be updated with valid data
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User edit all fields and click Save Changes
    • check_circleThen User should see messages "Changes Saved Your profile has been updated successfully!"
  • Validation on Account Information section for registered free user dashboard page Jul 4, 2025 04:13:18 PM Fail
    check_circle cancel clear
    00 01 13.228
    check_circle Scenario: Verify height should accept only Numeric Value
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User Edit height field with valid data
    • check_circleThen User should see that entered height is displayed in Height field
    00 01 45.513
    check_circle Scenario: Verify Weight should accept only Numeric Value
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User Edit Weight field with valid data
    • check_circleThen User should see that entered weight is displayed in Weight field
    00 02 07.898
    check_circle Scenario: Verify age should accept only Numeric Value
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User edit age field with valid data
    • check_circleThen User should see that entered age is displayed in that field
    00 01 45.942
    check_circle Scenario: Verify Exercise Routine Level dropdown is displayed with options
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User clicks the dropdown of Exercise Routine Level
    • check_circleThen User should see the dropdown with options "Easy","Medium","Hard"
    00 07 19.789
    cancel Scenario: Verify Cuisine Preferences dropdown is displayed with options
    • check_circleGiven User is in Home Page after logged in
    • cancelAnd User is in Dashboard page
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 00 28.436
    check_circle Scenario: Verify Food Allergies dropdown is displayed with options
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User clicks the dropdown of Food Allergies
    • check_circleThen User should see the dropdown list of common allergy options "None","Dairy","Gluten","Shellfish","Soy","Eggs","Nuts","Other"
    00 00 51.254
    check_circle Scenario: Verify account details cannot be updated with invalid data
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User edit with invalid data and click save changes
    • check_circleThen User should see Error message
    00 00 31.222
    check_circle Scenario: Verify account details can be updated with valid data
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User edit all fields and click Save Changes
    • check_circleThen User should see messages "Changes Saved Your profile has been updated successfully!"
  • Dashboard page validation for Registered Free account user Jul 4, 2025 04:13:19 PM Fail
    check_circle cancel clear
    00 02 08.919
    cancel Scenario: Verify all the fields under Account Information are Displayed
    • check_circleGiven User logged into the app
    • cancelThen User should see all the fields under Account Information section
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 17.075
    check_circle Scenario: Verify Upgrade to premium button is visible
    • check_circleGiven User logged into the app
    • check_circleThen User should see "Upgrade to Premium" button
    00 01 53.518
    check_circle Scenario: Verify the Welcome Message is displayed with name
    • check_circleGiven User logged into the app
    • check_circleGiven User is in Home Page
    • check_circleWhen User clicks the Dashboard on the navigation bar
    • check_circleThen User should see the "Welcome Back,full name" message
    00 00 43.016
    check_circle Scenario: Verify Save Changes button is visible
    • check_circleGiven User logged into the app
    • check_circleThen User should see "Save Changes" button
    00 01 39.186
    check_circle Scenario: Verify the text is displayed below welcome message
    • check_circleGiven User logged into the app
    • check_circleThen User should see the text "Track your metrics, manage your diet, and stay healthy with our comprehensive tools."
    00 01 34.129
    check_circle Scenario: Verify the header Account Information is present
    • check_circleGiven User logged into the app
    • check_circleThen User should see the header "Account Information" with correct spelling
  • Dashboard page validation for Registered Free account user Jul 4, 2025 04:13:19 PM Fail
    check_circle cancel clear
    00 00 50.220
    check_circle Scenario: Verify Save Changes button is visible
    • check_circleGiven User logged into the app
    • check_circleThen User should see "Save Changes" button
    00 01 35.145
    check_circle Scenario: Verify the text is displayed below welcome message
    • check_circleGiven User logged into the app
    • check_circleThen User should see the text "Track your metrics, manage your diet, and stay healthy with our comprehensive tools."
    00 00 47.255
    check_circle Scenario: Verify the header Account Information is present
    • check_circleGiven User logged into the app
    • check_circleThen User should see the header "Account Information" with correct spelling
    00 00 50.563
    check_circle Scenario: Verify Upgrade to premium button is visible
    • check_circleGiven User logged into the app
    • check_circleThen User should see "Upgrade to Premium" button
    00 03 05.528
    cancel Scenario: Verify all the fields under Account Information are Displayed
    • check_circleGiven User logged into the app
    • cancelThen User should see all the fields under Account Information section
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 04.542
    check_circle Scenario: Verify the Welcome Message is displayed with name
    • check_circleGiven User logged into the app
    • check_circleGiven User is in Home Page
    • check_circleWhen User clicks the Dashboard on the navigation bar
    • check_circleThen User should see the "Welcome Back,full name" message
  • Validation on Account Information section for registered free user dashboard page Jul 4, 2025 04:13:28 PM Fail
    check_circle cancel clear
    00 03 12.388
    check_circle Scenario: Verify age should accept only Numeric Value
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User edit age field with valid data
    • check_circleThen User should see that entered age is displayed in that field
    00 02 22.892
    cancel Scenario: Verify Exercise Routine Level dropdown is displayed with options
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • cancelWhen User clicks the dropdown of Exercise Routine Level
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 25.316
    check_circle Scenario: Verify Weight should accept only Numeric Value
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User Edit Weight field with valid data
    • check_circleThen User should see that entered weight is displayed in Weight field
    00 02 46.758
    check_circle Scenario: Verify height should accept only Numeric Value
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User Edit height field with valid data
    • check_circleThen User should see that entered height is displayed in Height field
    00 00 55.165
    check_circle Scenario: Verify Cuisine Preferences dropdown is displayed with options
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User clicks the dropdown of Cuisine Preferences
    • check_circleThen User should see the dropdown with list of cuisine types "Indian","American","Continental","Mediterranean","Asian","Middle Eastern","Mexican"
    00 01 43.748
    check_circle Scenario: Verify Food Allergies dropdown is displayed with options
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User clicks the dropdown of Food Allergies
    • check_circleThen User should see the dropdown list of common allergy options "None","Dairy","Gluten","Shellfish","Soy","Eggs","Nuts","Other"
    00 01 19.726
    check_circle Scenario: Verify account details cannot be updated with invalid data
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User edit with invalid data and click save changes
    • check_circleThen User should see Error message
    00 00 40.391
    check_circle Scenario: Verify account details can be updated with valid data
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in Dashboard page
    • check_circleWhen User edit all fields and click Save Changes
    • check_circleThen User should see messages "Changes Saved Your profile has been updated successfully!"
  • Dashboard page validation for Registered Free account user Jul 4, 2025 04:13:28 PM Fail
    check_circle cancel clear
    00 02 44.378
    check_circle Scenario: Verify the text is displayed below welcome message
    • check_circleGiven User logged into the app
    • check_circleThen User should see the text "Track your metrics, manage your diet, and stay healthy with our comprehensive tools."
    00 01 43.113
    check_circle Scenario: Verify Upgrade to premium button is visible
    • check_circleGiven User logged into the app
    • check_circleThen User should see "Upgrade to Premium" button
    00 02 50.390
    check_circle Scenario: Verify the Welcome Message is displayed with name
    • check_circleGiven User logged into the app
    • check_circleGiven User is in Home Page
    • check_circleWhen User clicks the Dashboard on the navigation bar
    • check_circleThen User should see the "Welcome Back,full name" message
    00 02 13.167
    cancel Scenario: Verify all the fields under Account Information are Displayed
    • check_circleGiven User logged into the app
    • cancelThen User should see all the fields under Account Information section
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 06.711
    check_circle Scenario: Verify the header Account Information is present
    • check_circleGiven User logged into the app
    • check_circleThen User should see the header "Account Information" with correct spelling
    00 02 06.799
    check_circle Scenario: Verify Save Changes button is visible
    • check_circleGiven User logged into the app
    • check_circleThen User should see "Save Changes" button
  • Validation on Stress Management Technique Section for Registered Free user dashboard page Jul 4, 2025 04:14:54 PM Fail
    check_circle cancel clear
    00 01 28.829
    cancel Scenario: Verify the header Stress Management Techniques
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • cancelWhen User scrolls to the Stress Management section
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _h_e_a_d_e_r_ _S_t_r_e_s_s_ _M_a_n_a_g_e_m_e_n_t_ _T_e_c_h_n_i_q_u_e_s_
    00 00 32.724
    check_circle Scenario: Verify the navigation bar order
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see tabs "Meditation", "Breathing", "Movement" and "Mindfulness"
    00 01 35.972
    check_circle Scenario: Verify tab navigation
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks on each tab
    • check_circleThen User should see corresponding display section
    00 01 21.805
    check_circle Scenario: Verify Guided Meditation section is visible
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks Meditation tab
    • check_circleThen User should see the content with title "Guided Meditation"
    00 00 55.484
    check_circle Scenario: Verify audio playback functionality
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks audio play button
    • check_circleThen User Should see meditation audio should start playing and the progress bar should update accordingly
    00 01 31.549
    check_circle Scenario: Verify the Title displayed under Movement tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks Movement Tab
    • check_circleThen User should see title "Gentle Movement"
    00 01 01.654
    cancel Scenario: Verify the title under Mindfulness tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks Mindfulness tab
    • cancelThen User should see title "Present Moment Awareness"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_t_l_e_ _u_n_d_e_r_ _M_i_n_d_f_u_l_n_e_s_s_ _t_a_b_
    00 01 20.292
    cancel Scenario: Verify heading and description is displayed under Breathing tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • cancelWhen User clicks breathing tab under stress management techniques
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _h_e_a_d_i_n_g_ _a_n_d_ _d_e_s_c_r_i_p_t_i_o_n_ _i_s_ _d_i_s_p_l_a_y_e_d_ _u_n_d_e_r_ _B_r_e_a_t_h_i_n_g_ _t_a_b_
    00 00 47.835
    check_circle Scenario: Verify Start button is displayed under Breathing tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see the "Start Breathing Exercise" button
    00 01 26.039
    check_circle Scenario: Verify Cycle completed counter is displayed
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see the "Cycles completed" counter text and value starting at 0
    00 01 38.552
    check_circle Scenario: Verify current phase counter is displayed
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see the label 'Current phase' with a hyphen (-) as its current value
    00 00 43.986
    check_circle Scenario: Verify stop button of breathing exercise
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks the "Stop" button during the breathing exercise
    • check_circleThen User should see breathing exercise stops
  • Validation on Stress Management Technique Section for Registered Free user dashboard page Jul 4, 2025 04:14:58 PM Fail
    check_circle cancel clear
    00 01 37.820
    cancel Scenario: Verify the header Stress Management Techniques
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • cancelWhen User scrolls to the Stress Management section
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _h_e_a_d_e_r_ _S_t_r_e_s_s_ _M_a_n_a_g_e_m_e_n_t_ _T_e_c_h_n_i_q_u_e_s_
    00 00 34.823
    check_circle Scenario: Verify the navigation bar order
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see tabs "Meditation", "Breathing", "Movement" and "Mindfulness"
    00 01 21.122
    check_circle Scenario: Verify tab navigation
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks on each tab
    • check_circleThen User should see corresponding display section
    00 01 28.518
    check_circle Scenario: Verify Guided Meditation section is visible
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks Meditation tab
    • check_circleThen User should see the content with title "Guided Meditation"
    00 07 10.394
    cancel Scenario: Verify audio playback functionality
    • check_circleGiven User is in Home Page after logged in
    • cancelAnd User is in the Dashboard Page
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 00 57.321
    check_circle Scenario: Verify the Title displayed under Movement tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks Movement Tab
    • check_circleThen User should see title "Gentle Movement"
    00 01 43.682
    cancel Scenario: Verify the title under Mindfulness tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks Mindfulness tab
    • cancelThen User should see title "Present Moment Awareness"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_t_l_e_ _u_n_d_e_r_ _M_i_n_d_f_u_l_n_e_s_s_ _t_a_b_
    00 01 31.284
    cancel Scenario: Verify heading and description is displayed under Breathing tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • cancelWhen User clicks breathing tab under stress management techniques
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _h_e_a_d_i_n_g_ _a_n_d_ _d_e_s_c_r_i_p_t_i_o_n_ _i_s_ _d_i_s_p_l_a_y_e_d_ _u_n_d_e_r_ _B_r_e_a_t_h_i_n_g_ _t_a_b_
    00 01 05.640
    check_circle Scenario: Verify Start button is displayed under Breathing tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see the "Start Breathing Exercise" button
    00 00 45.878
    check_circle Scenario: Verify Cycle completed counter is displayed
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see the "Cycles completed" counter text and value starting at 0
    00 00 39.192
    check_circle Scenario: Verify current phase counter is displayed
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see the label 'Current phase' with a hyphen (-) as its current value
    00 00 50.187
    check_circle Scenario: Verify stop button of breathing exercise
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks the "Stop" button during the breathing exercise
    • check_circleThen User should see breathing exercise stops
  • Validation on Stress Management Technique Section for Registered Free user dashboard page Jul 4, 2025 04:15:57 PM Fail
    check_circle cancel clear
    00 01 12.232
    cancel Scenario: Verify the header Stress Management Techniques
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • cancelWhen User scrolls to the Stress Management section
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _h_e_a_d_e_r_ _S_t_r_e_s_s_ _M_a_n_a_g_e_m_e_n_t_ _T_e_c_h_n_i_q_u_e_s_
    00 00 35.584
    check_circle Scenario: Verify the navigation bar order
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see tabs "Meditation", "Breathing", "Movement" and "Mindfulness"
    00 00 36.914
    check_circle Scenario: Verify tab navigation
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks on each tab
    • check_circleThen User should see corresponding display section
    00 01 17.524
    check_circle Scenario: Verify Guided Meditation section is visible
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks Meditation tab
    • check_circleThen User should see the content with title "Guided Meditation"
    00 00 50.090
    check_circle Scenario: Verify audio playback functionality
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks audio play button
    • check_circleThen User Should see meditation audio should start playing and the progress bar should update accordingly
    00 00 51.169
    check_circle Scenario: Verify the Title displayed under Movement tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks Movement Tab
    • check_circleThen User should see title "Gentle Movement"
    00 01 38.308
    cancel Scenario: Verify the title under Mindfulness tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks Mindfulness tab
    • cancelThen User should see title "Present Moment Awareness"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_t_l_e_ _u_n_d_e_r_ _M_i_n_d_f_u_l_n_e_s_s_ _t_a_b_
    00 01 36.217
    cancel Scenario: Verify heading and description is displayed under Breathing tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • cancelWhen User clicks breathing tab under stress management techniques
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _h_e_a_d_i_n_g_ _a_n_d_ _d_e_s_c_r_i_p_t_i_o_n_ _i_s_ _d_i_s_p_l_a_y_e_d_ _u_n_d_e_r_ _B_r_e_a_t_h_i_n_g_ _t_a_b_
    00 00 54.292
    check_circle Scenario: Verify Start button is displayed under Breathing tab
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see the "Start Breathing Exercise" button
    00 00 49.039
    check_circle Scenario: Verify Cycle completed counter is displayed
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see the "Cycles completed" counter text and value starting at 0
    00 00 48.328
    check_circle Scenario: Verify current phase counter is displayed
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleThen User should see the label 'Current phase' with a hyphen (-) as its current value
    00 01 06.260
    check_circle Scenario: Verify stop button of breathing exercise
    • check_circleGiven User is in Home Page after logged in
    • check_circleAnd User is in the Dashboard Page
    • check_circleWhen User clicks the "Stop" button during the breathing exercise
    • check_circleThen User should see breathing exercise stops
  • Validation for home page - Registered user Jul 4, 2025 04:16:26 PM Fail
    check_circle cancel clear
    00 00 34.564
    check_circle Scenario: Verify App name after sign in
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see SweetBalance text on the left side of the page
    00 00 47.007
    check_circle Scenario: Verify user name in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see name displayed at the top-right corner of the home page
    00 00 49.565
    check_circle Scenario: Verify the presence of logout link
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see Logout link in the top-right corner
    00 00 52.673
    check_circle Scenario: Verify the presence of top navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see top navigation bar on the page
    00 00 56.026
    check_circle Scenario: Verify the presence of Home text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Home" tab in the top navigation bar
    00 01 06.293
    check_circle Scenario: Verify the presence of Dashboard text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Dashboard" tab in the top navigation bar
    00 01 10.269
    check_circle Scenario: Verify the presence of Education text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Education" tab in the top navigation bar
    00 01 09.569
    check_circle Scenario: Verify the text "Current status" in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Current Status" section heading on the home page
    00 01 03.121
    check_circle Scenario: Verify the text "Last updated" in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Last updated" label below Current Status
    00 01 02.801
    check_circle Scenario: Verify the time for last update in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see timestamp displayed next to the "Last updated" label
    00 00 49.732
    check_circle Scenario: Verify the time format for last update
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see last updated timestamp in 12-hour format as hh:mm:ss or relative format like "3 min ago" or "2 hr ago"
    00 01 04.144
    cancel Scenario: Verify 12-hour clock indicator is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • cancelThen User should see 12-hour clock indicator with AM/PM
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _1_2_-_h_o_u_r_ _c_l_o_c_k_ _i_n_d_i_c_a_t_o_r_ _i_s_ _v_i_s_i_b_l_e_
    00 00 49.804
    check_circle Scenario: Verify Latest HbA1C label is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Latest HbA1C" label
    00 00 42.799
    check_circle Scenario: Verify BMI label is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "BMI" label
    00 00 40.672
    check_circle Scenario: Verify Average Blood Sugar label is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Average Blood Sugar" label
    00 01 16.180
    check_circle Scenario: Verify condition text for HbA1C value less than 5.7
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Normal" as the condition text
    00 01 24.996
    check_circle Scenario: Verify condition text for HbA1C between 5.7 and 6.4
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Pre-diabetic" as the condition text
    00 00 54.137
    check_circle Scenario: Verify condition text for HbA1C greater than or equal 6.5
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Diabetic" as the condition text
    00 00 50.948
    check_circle Scenario: Verify BMI text for value less than 18.5
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Underweight" as the BMI category
    00 00 54.225
    check_circle Scenario: Verify BMI text for value between 18.5 and 24.9
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Normal" as the BMI category
    00 00 53.950
    check_circle Scenario: Verify BMI text for value between 25.0 and 29.9
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Overweight" as the BMI category
    00 00 52.136
    check_circle Scenario: Verify BMI text for value 30.0 or above
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Obese" as the BMI category
    00 00 50.572
    check_circle Scenario: Verify units for average blood sugar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see mg/dL unit below Average Blood Sugar
    00 00 38.441
    check_circle Scenario: Verify title in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Today's Meal Plan" title
    00 00 36.239
    check_circle Scenario: Verify "Today’s Meal Plan" section is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see tabs: Breakfast, Lunch, Dinner, Snacks
    00 01 02.750
    check_circle Scenario: Verify Breakfast tab is selected by default
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen "Breakfast" tab should be selected by default
    00 00 42.492
    check_circle Scenario: Verify the presence of side tab in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see sidebar tab container within the flex layout
    00 01 09.443
    check_circle Scenario: Verify the text "Meal plan" in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Meal Plan" label in the sidebar section
    00 01 08.197
    check_circle Scenario: Verify the text "Exercise" in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Exercise" label in the sidebar section
    00 01 01.323
    check_circle Scenario: Verify the symbol utensil cross in "Meal plan"
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see utensil icon (crossed fork and knife) in the Meal Plan tab
    00 01 17.796
    check_circle Scenario: Verify the symbol dumbbell in "Exercise"
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see dumbbell icon in the Exercise tab
    00 01 09.321
    check_circle Scenario: Verify View Full Plan button is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "View Full Plan" button in the Meal Plan section
  • Validation for home page - Registered user Jul 4, 2025 04:16:56 PM Fail
    check_circle cancel clear
    00 00 47.515
    check_circle Scenario: Verify App name after sign in
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see SweetBalance text on the left side of the page
    00 00 45.775
    check_circle Scenario: Verify user name in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see name displayed at the top-right corner of the home page
    00 01 02.159
    check_circle Scenario: Verify the presence of logout link
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see Logout link in the top-right corner
    00 01 01.409
    check_circle Scenario: Verify the presence of top navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see top navigation bar on the page
    00 01 01.359
    check_circle Scenario: Verify the presence of Home text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Home" tab in the top navigation bar
    00 00 52.660
    check_circle Scenario: Verify the presence of Dashboard text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Dashboard" tab in the top navigation bar
    00 00 48.693
    check_circle Scenario: Verify the presence of Education text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Education" tab in the top navigation bar
    00 00 48.815
    check_circle Scenario: Verify the text "Current status" in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Current Status" section heading on the home page
    00 00 46.781
    check_circle Scenario: Verify the text "Last updated" in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Last updated" label below Current Status
    00 00 46.903
    check_circle Scenario: Verify the time for last update in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see timestamp displayed next to the "Last updated" label
    00 01 23.572
    cancel Scenario: Verify 12-hour clock indicator is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • cancelThen User should see 12-hour clock indicator with AM/PM
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _1_2_-_h_o_u_r_ _c_l_o_c_k_ _i_n_d_i_c_a_t_o_r_ _i_s_ _v_i_s_i_b_l_e_
    00 01 00.632
    check_circle Scenario: Verify the time format for last update
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see last updated timestamp in 12-hour format as hh:mm:ss or relative format like "3 min ago" or "2 hr ago"
    00 01 14.884
    check_circle Scenario: Verify Latest HbA1C label is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Latest HbA1C" label
    00 00 56.962
    check_circle Scenario: Verify BMI label is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "BMI" label
    00 00 50.638
    check_circle Scenario: Verify Average Blood Sugar label is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Average Blood Sugar" label
    00 00 57.577
    check_circle Scenario: Verify condition text for HbA1C value less than 5.7
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Normal" as the condition text
    00 01 13.311
    check_circle Scenario: Verify condition text for HbA1C between 5.7 and 6.4
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Pre-diabetic" as the condition text
    00 00 57.051
    check_circle Scenario: Verify condition text for HbA1C greater than or equal 6.5
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Diabetic" as the condition text
    00 00 53.741
    check_circle Scenario: Verify BMI text for value less than 18.5
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Underweight" as the BMI category
    00 00 37.822
    check_circle Scenario: Verify BMI text for value between 18.5 and 24.9
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Normal" as the BMI category
    00 00 34.110
    check_circle Scenario: Verify BMI text for value between 25.0 and 29.9
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Overweight" as the BMI category
    00 00 42.562
    check_circle Scenario: Verify BMI text for value 30.0 or above
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Obese" as the BMI category
    00 00 46.158
    check_circle Scenario: Verify units for average blood sugar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see mg/dL unit below Average Blood Sugar
    00 00 56.749
    check_circle Scenario: Verify title in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Today's Meal Plan" title
    00 00 42.559
    check_circle Scenario: Verify "Today’s Meal Plan" section is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see tabs: Breakfast, Lunch, Dinner, Snacks
    00 01 05.797
    check_circle Scenario: Verify Breakfast tab is selected by default
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen "Breakfast" tab should be selected by default
    00 01 05.393
    check_circle Scenario: Verify the presence of side tab in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see sidebar tab container within the flex layout
    00 01 15.263
    check_circle Scenario: Verify the text "Meal plan" in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Meal Plan" label in the sidebar section
    00 01 12.191
    check_circle Scenario: Verify the text "Exercise" in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Exercise" label in the sidebar section
    00 00 57.000
    check_circle Scenario: Verify the symbol utensil cross in "Meal plan"
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see utensil icon (crossed fork and knife) in the Meal Plan tab
    00 00 51.148
    check_circle Scenario: Verify the symbol dumbbell in "Exercise"
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see dumbbell icon in the Exercise tab
    00 00 56.743
    check_circle Scenario: Verify View Full Plan button is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "View Full Plan" button in the Meal Plan section
  • Validation for home page - Registered user Jul 4, 2025 04:17:09 PM Fail
    check_circle cancel clear
    00 00 59.599
    check_circle Scenario: Verify App name after sign in
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see SweetBalance text on the left side of the page
    00 01 00.070
    check_circle Scenario: Verify user name in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see name displayed at the top-right corner of the home page
    00 00 56.776
    check_circle Scenario: Verify the presence of logout link
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see Logout link in the top-right corner
    00 00 50.571
    check_circle Scenario: Verify the presence of top navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see top navigation bar on the page
    00 00 48.386
    check_circle Scenario: Verify the presence of Home text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Home" tab in the top navigation bar
    00 01 01.455
    check_circle Scenario: Verify the presence of Dashboard text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Dashboard" tab in the top navigation bar
    00 01 41.311
    check_circle Scenario: Verify the presence of Education text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Education" tab in the top navigation bar
    00 00 54.055
    check_circle Scenario: Verify the text "Current status" in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Current Status" section heading on the home page
    00 00 57.704
    check_circle Scenario: Verify the text "Last updated" in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Last updated" label below Current Status
    00 00 58.038
    check_circle Scenario: Verify the time for last update in home page
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see timestamp displayed next to the "Last updated" label
    00 01 12.260
    check_circle Scenario: Verify the time format for last update
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see last updated timestamp in 12-hour format as hh:mm:ss or relative format like "3 min ago" or "2 hr ago"
    00 01 18.493
    cancel Scenario: Verify 12-hour clock indicator is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • cancelThen User should see 12-hour clock indicator with AM/PM
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _1_2_-_h_o_u_r_ _c_l_o_c_k_ _i_n_d_i_c_a_t_o_r_ _i_s_ _v_i_s_i_b_l_e_
    00 01 09.087
    check_circle Scenario: Verify Latest HbA1C label is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Latest HbA1C" label
    00 01 01.930
    check_circle Scenario: Verify BMI label is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "BMI" label
    00 00 55.255
    check_circle Scenario: Verify Average Blood Sugar label is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Average Blood Sugar" label
    00 00 53.950
    check_circle Scenario: Verify condition text for HbA1C value less than 5.7
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Normal" as the condition text
    00 00 44.393
    check_circle Scenario: Verify condition text for HbA1C between 5.7 and 6.4
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Pre-diabetic" as the condition text
    00 00 33.836
    check_circle Scenario: Verify condition text for HbA1C greater than or equal 6.5
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Diabetic" as the condition text
    00 00 43.117
    check_circle Scenario: Verify BMI text for value less than 18.5
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Underweight" as the BMI category
    00 00 49.150
    check_circle Scenario: Verify BMI text for value between 18.5 and 24.9
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Normal" as the BMI category
    00 01 03.576
    check_circle Scenario: Verify BMI text for value between 25.0 and 29.9
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Overweight" as the BMI category
    00 01 01.193
    check_circle Scenario: Verify BMI text for value 30.0 or above
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Obese" as the BMI category
    00 00 41.150
    check_circle Scenario: Verify units for average blood sugar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see mg/dL unit below Average Blood Sugar
    00 00 43.120
    check_circle Scenario: Verify title in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Today's Meal Plan" title
    00 01 22.381
    check_circle Scenario: Verify "Today’s Meal Plan" section is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see tabs: Breakfast, Lunch, Dinner, Snacks
    00 01 05.229
    check_circle Scenario: Verify Breakfast tab is selected by default
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen "Breakfast" tab should be selected by default
    00 01 14.877
    check_circle Scenario: Verify the presence of side tab in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see sidebar tab container within the flex layout
    00 00 59.161
    check_circle Scenario: Verify the text "Meal plan" in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Meal Plan" label in the sidebar section
    00 00 47.968
    check_circle Scenario: Verify the text "Exercise" in flex container
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "Exercise" label in the sidebar section
    00 01 00.617
    check_circle Scenario: Verify the symbol utensil cross in "Meal plan"
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see utensil icon (crossed fork and knife) in the Meal Plan tab
    00 00 57.272
    check_circle Scenario: Verify the symbol dumbbell in "Exercise"
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see dumbbell icon in the Exercise tab
    00 01 28.022
    check_circle Scenario: Verify View Full Plan button is visible
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see "View Full Plan" button in the Meal Plan section
  • Home Page Navigation for Free Registered Users Jul 4, 2025 04:19:52 PM Fail
    check_circle cancel clear
    00 00 55.685
    check_circle Scenario: Verify order of text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see the navigation bar displaying items in the order: Home, Dashboard, Education
    00 00 53.807
    cancel Scenario: Verify the presence of collapse toggle
    • cancelThen User should see a caret toggle icon next to the "Today's Meal Plan" title
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _c_o_l_l_a_p_s_e_ _t_o_g_g_l_e_
  • Home Page Navigation for Free Registered Users Jul 4, 2025 04:20:15 PM Fail
    check_circle cancel clear
    00 00 58.024
    check_circle Scenario: Verify order of text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see the navigation bar displaying items in the order: Home, Dashboard, Education
    00 01 20.063
    cancel Scenario: Verify the presence of collapse toggle
    • cancelThen User should see a caret toggle icon next to the "Today's Meal Plan" title
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _c_o_l_l_a_p_s_e_ _t_o_g_g_l_e_
  • Home Page Navigation for Free Registered Users Jul 4, 2025 04:20:29 PM Fail
    check_circle cancel clear
    00 01 26.594
    check_circle Scenario: Verify order of text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see the navigation bar displaying items in the order: Home, Dashboard, Education
    00 01 18.516
    cancel Scenario: Verify the presence of collapse toggle
    • cancelThen User should see a caret toggle icon next to the "Today's Meal Plan" title
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _c_o_l_l_a_p_s_e_ _t_o_g_g_l_e_
  • Functional and non-functional test validation for home page Jul 4, 2025 04:20:30 PM Fail
    check_circle cancel clear
    00 01 45.205
    check_circle Scenario: Verify meal section contains dish title
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see dish title
    00 01 32.354
    check_circle Scenario: Verify meal section contains dish description
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see description for the dish
    00 02 40.096
    cancel Scenario: Verify pre-meal item is shown for each meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see the pre-meal item name
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 35.719
    cancel Scenario: Verify calories for pre-meal is shown for each meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see the pre-meal calorie value
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 08.085
    check_circle Scenario: Validate the indicator for breakfast pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see indicator "AM" for breakfast pre-meal
    00 01 04.475
    check_circle Scenario: Validate the indicator for lunch pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see indicator "PM" for lunch pre-meal
    00 01 03.824
    check_circle Scenario: Validate the indicator for dinner pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see indicator "PM" for dinner pre-meal
    00 00 58.455
    check_circle Scenario: Verify the time format in each pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see "hh:mm" based time in pre-meal (eg : 1:00)
    00 01 47.389
    check_circle Scenario: Verify the time in pre-breakfast
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see 7'o clock
    00 03 32.315
    cancel Scenario: Verify the time in pre-lunch
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see the 12 o'clock
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 51.702
    check_circle Scenario: Verify the time in pre-dinner
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see 7'o clock
    00 01 26.292
    check_circle Scenario: Verify Carbs bar color for each meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see green color for Carbs
    00 01 51.092
    check_circle Scenario: Verify Fat bar color
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see purple color for Fat
    00 01 13.445
    check_circle Scenario: Verify Protein bar color
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see pink color for Protein
    00 07 25.456
    cancel Scenario: Verify unit of measurement for Carbs is in grams
    • cancelGiven User is logged into the app
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 09.088
    check_circle Scenario: Verify unit of measurement for Protein is in grams
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen It should display the unit as "g"
    00 06 49.229
    cancel Scenario: Verify unit of measurement for Fat is in grams
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 06 36.140
    cancel Scenario: Validate the text "calories" in pre-meal
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Functional and non-functional test validation for home page Jul 4, 2025 04:20:42 PM Fail
    check_circle cancel clear
    00 01 33.596
    check_circle Scenario: Verify meal section contains dish title
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see dish title
    00 01 11.910
    check_circle Scenario: Verify meal section contains dish description
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see description for the dish
    00 01 53.783
    cancel Scenario: Verify pre-meal item is shown for each meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see the pre-meal item name
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_r_e_-_m_e_a_l_ _i_t_e_m_ _i_s_ _s_h_o_w_n_ _f_o_r_ _e_a_c_h_ _m_e_a_l_
    00 01 24.324
    cancel Scenario: Verify calories for pre-meal is shown for each meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see the pre-meal calorie value
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _c_a_l_o_r_i_e_s_ _f_o_r_ _p_r_e_-_m_e_a_l_ _i_s_ _s_h_o_w_n_ _f_o_r_ _e_a_c_h_ _m_e_a_l_
    00 01 01.612
    check_circle Scenario: Validate the indicator for breakfast pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see indicator "AM" for breakfast pre-meal
    00 06 44.591
    cancel Scenario: Validate the indicator for lunch pre-meal
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 06 37.620
    cancel Scenario: Validate the indicator for dinner pre-meal
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 12.862
    check_circle Scenario: Verify the time format in each pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see "hh:mm" based time in pre-meal (eg : 1:00)
    00 01 08.578
    check_circle Scenario: Verify the time in pre-breakfast
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see 7'o clock
    00 01 53.416
    cancel Scenario: Verify the time in pre-lunch
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see the 12 o'clock
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_m_e_ _i_n_ _p_r_e_-_l_u_n_c_h_
    00 01 33.320
    check_circle Scenario: Verify the time in pre-dinner
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see 7'o clock
    00 01 50.073
    check_circle Scenario: Verify Carbs bar color for each meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see green color for Carbs
    00 01 43.076
    check_circle Scenario: Verify Fat bar color
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see purple color for Fat
    00 07 25.261
    cancel Scenario: Verify Protein bar color
    • cancelGiven User is logged into the app
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 04.610
    check_circle Scenario: Verify unit of measurement for Carbs is in grams
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen It should display the unit as "g"
    00 01 44.487
    check_circle Scenario: Verify unit of measurement for Protein is in grams
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen It should display the unit as "g"
    00 01 22.635
    check_circle Scenario: Verify unit of measurement for Fat is in grams
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen It should display the unit as "g"
    00 02 26.184
    cancel Scenario: Validate the text "calories" in pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see text "calories" after the calorie value in pre meal
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_a_l_i_d_a_t_e_ _t_h_e_ _t_e_x_t_ _"_c_a_l_o_r_i_e_s_"_ _i_n_ _p_r_e_-_m_e_a_l_
  • Functional and non-functional test validation for home page Jul 4, 2025 04:20:45 PM Fail
    check_circle cancel clear
    00 01 11.294
    check_circle Scenario: Verify meal section contains dish title
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see dish title
    00 01 11.600
    check_circle Scenario: Verify meal section contains dish description
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see description for the dish
    00 01 49.652
    cancel Scenario: Verify pre-meal item is shown for each meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see the pre-meal item name
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_r_e_-_m_e_a_l_ _i_t_e_m_ _i_s_ _s_h_o_w_n_ _f_o_r_ _e_a_c_h_ _m_e_a_l_
    00 01 24.664
    cancel Scenario: Verify calories for pre-meal is shown for each meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see the pre-meal calorie value
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _c_a_l_o_r_i_e_s_ _f_o_r_ _p_r_e_-_m_e_a_l_ _i_s_ _s_h_o_w_n_ _f_o_r_ _e_a_c_h_ _m_e_a_l_
    00 01 01.650
    check_circle Scenario: Validate the indicator for breakfast pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see indicator "AM" for breakfast pre-meal
    00 06 36.331
    cancel Scenario: Validate the indicator for lunch pre-meal
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 00.153
    check_circle Scenario: Validate the indicator for dinner pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see indicator "PM" for dinner pre-meal
    00 01 31.184
    check_circle Scenario: Verify the time format in each pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see "hh:mm" based time in pre-meal (eg : 1:00)
    00 01 37.226
    check_circle Scenario: Verify the time in pre-breakfast
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see 7'o clock
    00 02 17.786
    cancel Scenario: Verify the time in pre-lunch
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see the 12 o'clock
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_m_e_ _i_n_ _p_r_e_-_l_u_n_c_h_
    00 01 54.594
    check_circle Scenario: Verify the time in pre-dinner
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see 7'o clock
    00 01 54.525
    check_circle Scenario: Verify Carbs bar color for each meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see green color for Carbs
    00 01 25.672
    check_circle Scenario: Verify Fat bar color
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see purple color for Fat
    00 01 05.301
    check_circle Scenario: Verify Protein bar color
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see pink color for Protein
    00 02 09.666
    check_circle Scenario: Verify unit of measurement for Carbs is in grams
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen It should display the unit as "g"
    00 06 51.097
    cancel Scenario: Verify unit of measurement for Protein is in grams
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 06 45.315
    cancel Scenario: Verify unit of measurement for Fat is in grams
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 18.169
    cancel Scenario: Validate the text "calories" in pre-meal
    • check_circleGiven User is logged into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • cancelThen User should see text "calories" after the calorie value in pre meal
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_a_l_i_d_a_t_e_ _t_h_e_ _t_e_x_t_ _"_c_a_l_o_r_i_e_s_"_ _i_n_ _p_r_e_-_m_e_a_l_
  • Home Page Validation for Registered Free Account User Jul 4, 2025 04:23:28 PM Fail
    check_circle cancel clear
    00 02 07.394
    check_circle Scenario: Verify order of text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see the navigation bar displaying items in the order: Home, Dashboard, Education
    00 01 46.910
    cancel Scenario: Verify the presence of collapse toggle
    • check_circleGiven User is in password auth page
    • cancelThen User should see a caret toggle icon next to the "Today's Meal Plan" title
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _c_o_l_l_a_p_s_e_ _t_o_g_g_l_e_
  • Home Page Validation for Registered Free Account User Jul 4, 2025 04:23:29 PM Fail
    check_circle cancel clear
    00 01 26.851
    check_circle Scenario: Verify order of text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see the navigation bar displaying items in the order: Home, Dashboard, Education
    00 01 44.957
    cancel Scenario: Verify the presence of collapse toggle
    • check_circleGiven User is in password auth page
    • cancelThen User should see a caret toggle icon next to the "Today's Meal Plan" title
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _c_o_l_l_a_p_s_e_ _t_o_g_g_l_e_
  • Meal and Exercise Section Validation for Registered Free Account User Jul 4, 2025 04:23:30 PM Fail
    check_circle cancel clear
    00 01 47.457
    check_circle Scenario: Verify the presence of "Nutrition Insights" heading
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see "Nutrition Insights" heading for each of the meal section
    00 01 42.537
    check_circle Scenario: Verify the presence of Carbs value for nutrition
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see Carbs value for the main
    00 01 29.309
    check_circle Scenario: Verify the presence of Protein value for nutrition
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see Protein value for the main
    00 01 28.313
    check_circle Scenario: Verify the presence of Fat value for nutrition
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see Fat value for the main meal
    00 01 28.558
    check_circle Scenario: Verify the time format in pre-meal snack
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see "hh:mm" based time in pre-meal snack (eg: 1:00)
    00 01 00.886
    check_circle Scenario: Verify the time in pre-snack
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see 3 o'clock
    00 01 22.095
    check_circle Scenario: Verify the navigation of "View Full Plan" button
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks "View Full Plan" button
    • check_circleThen User should be redirected to subscription page
    00 02 03.361
    cancel Scenario: Verify the title in Exercise section
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks exercise section
    • cancelThen User should see title "Today's Exercise Plan"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_t_l_e_ _i_n_ _E_x_e_r_c_i_s_e_ _s_e_c_t_i_o_n_
    00 01 53.595
    check_circle Scenario: Verify the presence of exercise list
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see exercises list for the day
    00 01 47.826
    check_circle Scenario: Verify the presence of time in each exercise
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see scheduled time of each exercise
    00 01 42.044
    check_circle Scenario: Verify the time for morning exercise
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen Morning exercise should be scheduled for 7 o'clock
    00 01 08.856
    check_circle Scenario: Verify the time for evening exercise
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen Evening exercise should be scheduled for 5 o'clock
    00 01 11.077
    check_circle Scenario: Verify the title for each exercise plan
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see plan title for each exercise
    00 01 09.795
    check_circle Scenario: Verify the presence of duration in each exercise plan
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see a duration in each exercise item
    00 00 57.372
    check_circle Scenario: Verify the presence of "View Full Schedule" button
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see button with text "View Full Schedule"
    00 02 21.768
    cancel Scenario: Verify the navigation of "View Full Schedule" button
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • cancelWhen User clicks view full schedule button after reaching exercise section
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _"_V_i_e_w_ _F_u_l_l_ _S_c_h_e_d_u_l_e_"_ _b_u_t_t_o_n_
  • Home Page Validation for Registered Free Account User Jul 4, 2025 04:23:30 PM Fail
    check_circle cancel clear
    00 01 46.624
    check_circle Scenario: Verify order of text in navigation bar
    • check_circleGiven User is in password auth page
    • check_circleWhen User clicks sign in after entering password
    • check_circleThen User should see the navigation bar displaying items in the order: Home, Dashboard, Education
    00 01 54.963
    cancel Scenario: Verify the presence of collapse toggle
    • check_circleGiven User is in password auth page
    • cancelThen User should see a caret toggle icon next to the "Today's Meal Plan" title
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _c_o_l_l_a_p_s_e_ _t_o_g_g_l_e_
  • Meal and Exercise Section Validation for Registered Free Account User Jul 4, 2025 04:23:51 PM Fail
    check_circle cancel clear
    00 01 45.281
    check_circle Scenario: Verify the presence of "Nutrition Insights" heading
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks meal section
    • check_circleThen User should see "Nutrition Insights" heading for each of the meal section
    00 01 44.500
    check_circle Scenario: Verify the presence of Carbs value for nutrition
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see Carbs value for the main
    00 01 28.214
    check_circle Scenario: Verify the presence of Protein value for nutrition
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see Protein value for the main
    00 01 07.024
    check_circle Scenario: Verify the presence of Fat value for nutrition
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see Fat value for the main meal
    00 00 57.647
    check_circle Scenario: Verify the time format in pre-meal snack
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see "hh:mm" based time in pre-meal snack (eg: 1:00)
    00 00 51.400
    check_circle Scenario: Verify the time in pre-snack
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see 3 o'clock
    00 01 31.926
    check_circle Scenario: Verify the navigation of "View Full Plan" button
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks "View Full Plan" button
    • check_circleThen User should be redirected to subscription page
    00 03 16.783
    cancel Scenario: Verify the title in Exercise section
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks exercise section
    • cancelThen User should see title "Today's Exercise Plan"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 18.517
    check_circle Scenario: Verify the presence of exercise list
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see exercises list for the day
    00 01 00.310
    check_circle Scenario: Verify the presence of time in each exercise
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see scheduled time of each exercise
    00 01 04.435
    check_circle Scenario: Verify the time for morning exercise
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen Morning exercise should be scheduled for 7 o'clock
    00 01 23.061
    check_circle Scenario: Verify the time for evening exercise
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen Evening exercise should be scheduled for 5 o'clock
    00 01 14.054
    check_circle Scenario: Verify the title for each exercise plan
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see plan title for each exercise
    00 00 57.995
    check_circle Scenario: Verify the presence of duration in each exercise plan
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see a duration in each exercise item
    00 00 54.139
    check_circle Scenario: Verify the presence of "View Full Schedule" button
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see button with text "View Full Schedule"
    00 01 16.076
    cancel Scenario: Verify the navigation of "View Full Schedule" button
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • cancelWhen User clicks view full schedule button after reaching exercise section
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _"_V_i_e_w_ _F_u_l_l_ _S_c_h_e_d_u_l_e_"_ _b_u_t_t_o_n_
  • Meal and Exercise Section Validation for Registered Free Account User Jul 4, 2025 04:23:51 PM Fail
    check_circle cancel clear
    00 07 34.889
    cancel Scenario: Verify the presence of "Nutrition Insights" heading
    • cancelGiven User logs into the app
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 40.030
    check_circle Scenario: Verify the presence of Carbs value for nutrition
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see Carbs value for the main
    00 01 24.083
    check_circle Scenario: Verify the presence of Protein value for nutrition
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see Protein value for the main
    00 01 44.832
    check_circle Scenario: Verify the presence of Fat value for nutrition
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see Fat value for the main meal
    00 01 30.146
    check_circle Scenario: Verify the time format in pre-meal snack
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see "hh:mm" based time in pre-meal snack (eg: 1:00)
    00 01 28.977
    check_circle Scenario: Verify the time in pre-snack
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see 3 o'clock
    00 02 01.933
    check_circle Scenario: Verify the navigation of "View Full Plan" button
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks "View Full Plan" button
    • check_circleThen User should be redirected to subscription page
    00 02 24.176
    cancel Scenario: Verify the title in Exercise section
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleWhen User clicks exercise section
    • cancelThen User should see title "Today's Exercise Plan"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_t_l_e_ _i_n_ _E_x_e_r_c_i_s_e_ _s_e_c_t_i_o_n_
    00 01 03.899
    check_circle Scenario: Verify the presence of exercise list
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see exercises list for the day
    00 06 44.830
    cancel Scenario: Verify the presence of time in each exercise
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 01.518
    check_circle Scenario: Verify the time for morning exercise
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen Morning exercise should be scheduled for 7 o'clock
    00 01 04.714
    check_circle Scenario: Verify the time for evening exercise
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen Evening exercise should be scheduled for 5 o'clock
    00 00 54.059
    check_circle Scenario: Verify the title for each exercise plan
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see plan title for each exercise
    00 01 59.766
    check_circle Scenario: Verify the presence of duration in each exercise plan
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see a duration in each exercise item
    00 01 16.269
    check_circle Scenario: Verify the presence of "View Full Schedule" button
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • check_circleThen User should see button with text "View Full Schedule"
    00 01 30.849
    cancel Scenario: Verify the navigation of "View Full Schedule" button
    • check_circleGiven User logs into the app
    • check_circleGiven User is in home page
    • cancelWhen User clicks view full schedule button after reaching exercise section
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _"_V_i_e_w_ _F_u_l_l_ _S_c_h_e_d_u_l_e_"_ _b_u_t_t_o_n_
  • Upgrade to Premium Subscription Jul 4, 2025 04:27:08 PM Fail
    check_circle cancel clear
    00 02 33.816
    check_circle Scenario: Verify user is unable to proceed with empty payment fields
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • check_circleWhen User clicks the "Pay $9.99 USD" button without entering any card details
    • check_circleThen User should see validation messages for all required fields
    00 02 05.427
    cancel Scenario: Verify user is unable to proceed with invalid card number
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • cancelWhen User enters an invalid card number
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _i_s_ _u_n_a_b_l_e_ _t_o_ _p_r_o_c_e_e_d_ _w_i_t_h_ _i_n_v_a_l_i_d_ _c_a_r_d_ _n_u_m_b_e_r_
    00 02 24.448
    cancel Scenario: Verify user is unable to proceed with expired card
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • cancelWhen User enters an expired card
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _i_s_ _u_n_a_b_l_e_ _t_o_ _p_r_o_c_e_e_d_ _w_i_t_h_ _e_x_p_i_r_e_d_ _c_a_r_d_
    00 02 15.873
    cancel Scenario: Verify user can successfully upgrade with valid payment details
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • check_circleWhen User enters valid payment details
    • check_circleAnd User clicks the "Pay $9.99 USD" button
    • cancelThen User should be redirected to the confirmation or home page with premium access enabled
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _c_a_n_ _s_u_c_c_e_s_s_f_u_l_l_y_ _u_p_g_r_a_d_e_ _w_i_t_h_ _v_a_l_i_d_ _p_a_y_m_e_n_t_ _d_e_t_a_i_l_s_
  • Upgrade to Premium Subscription Jul 4, 2025 04:27:18 PM Fail
    check_circle cancel clear
    00 02 18.532
    check_circle Scenario: Verify user is unable to proceed with empty payment fields
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • check_circleWhen User clicks the "Pay $9.99 USD" button without entering any card details
    • check_circleThen User should see validation messages for all required fields
    00 02 10.779
    cancel Scenario: Verify user is unable to proceed with invalid card number
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • cancelWhen User enters an invalid card number
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _i_s_ _u_n_a_b_l_e_ _t_o_ _p_r_o_c_e_e_d_ _w_i_t_h_ _i_n_v_a_l_i_d_ _c_a_r_d_ _n_u_m_b_e_r_
    00 02 19.574
    cancel Scenario: Verify user is unable to proceed with expired card
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • cancelWhen User enters an expired card
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _i_s_ _u_n_a_b_l_e_ _t_o_ _p_r_o_c_e_e_d_ _w_i_t_h_ _e_x_p_i_r_e_d_ _c_a_r_d_
    00 02 05.720
    cancel Scenario: Verify user can successfully upgrade with valid payment details
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • check_circleWhen User enters valid payment details
    • check_circleAnd User clicks the "Pay $9.99 USD" button
    • cancelThen User should be redirected to the confirmation or home page with premium access enabled
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _c_a_n_ _s_u_c_c_e_s_s_f_u_l_l_y_ _u_p_g_r_a_d_e_ _w_i_t_h_ _v_a_l_i_d_ _p_a_y_m_e_n_t_ _d_e_t_a_i_l_s_
  • Upgrade to Premium Subscription Jul 4, 2025 04:27:49 PM Fail
    check_circle cancel clear
    00 01 56.621
    check_circle Scenario: Verify user is unable to proceed with empty payment fields
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • check_circleWhen User clicks the "Pay $9.99 USD" button without entering any card details
    • check_circleThen User should see validation messages for all required fields
    00 02 15.501
    cancel Scenario: Verify user is unable to proceed with invalid card number
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • cancelWhen User enters an invalid card number
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _i_s_ _u_n_a_b_l_e_ _t_o_ _p_r_o_c_e_e_d_ _w_i_t_h_ _i_n_v_a_l_i_d_ _c_a_r_d_ _n_u_m_b_e_r_
    00 02 09.499
    cancel Scenario: Verify user is unable to proceed with expired card
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • cancelWhen User enters an expired card
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _i_s_ _u_n_a_b_l_e_ _t_o_ _p_r_o_c_e_e_d_ _w_i_t_h_ _e_x_p_i_r_e_d_ _c_a_r_d_
    00 02 10.717
    cancel Scenario: Verify user can successfully upgrade with valid payment details
    • check_circleGiven User is on the subscription page
    • check_circleAnd User clicks the "Upgrade to Premium" button
    • check_circleWhen User enters valid payment details
    • check_circleAnd User clicks the "Pay $9.99 USD" button
    • cancelThen User should be redirected to the confirmation or home page with premium access enabled
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _c_a_n_ _s_u_c_c_e_s_s_f_u_l_l_y_ _u_p_g_r_a_d_e_ _w_i_t_h_ _v_a_l_i_d_ _p_a_y_m_e_n_t_ _d_e_t_a_i_l_s_
  • Premium User Exercise Schedule Functionality Jul 4, 2025 04:27:54 PM Fail
    check_circle cancel clear
    00 00 45.228
    check_circle Scenario: Verify "View Full Schedule" button is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "View Full Schedule" button is displayed on the right
    00 00 42.314
    check_circle Scenario: Verify navigation to "Today's Exercise Schedule" page
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "View Full Schedule" button
    • check_circleThen User is redirected to "Today's Exercise Schedule" page
    00 00 52.974
    check_circle Scenario: Verify "Warm Up" tab is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Warm Up" tab is visible
    00 00 43.173
    check_circle Scenario: Verify "Main Workout" tab is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Main Workout" tab is visible
    00 00 47.906
    check_circle Scenario: Verify "Cool Down" tab is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Cool Down" tab is visible
    00 00 44.242
    check_circle Scenario: Verify Exercise name is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Exercise name is displayed under "Warm Up" tab
    00 00 44.527
    check_circle Scenario: Verify Exercise name is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Exercise name is displayed under "Main Workout" tab
    00 00 39.204
    check_circle Scenario: Verify Exercise name is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Exercise name is displayed under "Cool Down" tab
    00 00 39.172
    check_circle Scenario: Verify Exercise description is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Description is shown below the Exercise name under "Warm Up"
    00 00 42.675
    check_circle Scenario: Verify Exercise description is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Description is shown below the Exercise name under "Main Workout"
    00 00 38.891
    check_circle Scenario: Verify Exercise description is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Description is shown below the Exercise name under "Cool Down"
    00 00 35.984
    check_circle Scenario: Verify duration is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Duration is displayed under "Warm Up" tab
    00 00 33.510
    check_circle Scenario: Verify calories are displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Calories are displayed under "Warm Up" tab
    00 00 32.655
    check_circle Scenario: Verify intensity level is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Intensity level is displayed under "Warm Up" tab
    00 00 46.811
    check_circle Scenario: Verify duration is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Duration is displayed under "Main Workout" tab
    00 00 46.347
    check_circle Scenario: Verify calories are displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Calories are displayed under "Main Workout" tab
    00 06 49.967
    cancel Scenario: Verify intensity level is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 00 45.513
    check_circle Scenario: Verify duration is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Duration is displayed under "Cool Down" tab
    00 00 46.416
    check_circle Scenario: Verify calories are displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Calories are displayed under "Cool Down" tab
    00 00 44.552
    check_circle Scenario: Verify intensity level is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Intensity level is displayed under "Cool Down" tab
    00 00 42.382
    check_circle Scenario: Verify "Mark As Completed" button is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Mark As Completed" button is displayed for all three sections
    00 00 39.631
    check_circle Scenario: Verify success dialog is shown after marking as completed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Mark As Completed" button
    • check_circleThen Success dialog is shown
    00 00 39.708
    check_circle Scenario: Verify button status changes to "Completed"
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Mark As Completed" button
    • check_circleThen Button changes to "Completed"
    00 00 38.768
    check_circle Scenario: Verify undo option is displayed after marking completed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Mark As Completed" button
    • check_circleThen Undo option is visible
    00 01 06.883
    check_circle Scenario: Verify button reverts back after undo
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks Undo after marking Exercise as completed
    • check_circleThen Button changes back to "Mark As Completed"
    00 00 28.392
    check_circle Scenario: Verify navigation to "View full schedule"
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen User should redirect to Exercise schedule
    00 01 02.428
    cancel Scenario: Verify page title is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • cancelThen User should see title "Today's Exercise Schedule"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_a_g_e_ _t_i_t_l_e_ _i_s_ _d_i_s_p_l_a_y_e_d_
    00 00 25.429
    check_circle Scenario: Verify "Back to Home" button is visible
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen User should see "Back to Home" button in Today's Exercise schedule page
    00 00 39.718
    check_circle Scenario: Verify "Warm Up" section is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" section should be visible
    00 00 48.474
    check_circle Scenario: Verify warm-up exercise name
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen Exercise name should be visible
    00 00 36.135
    check_circle Scenario: Verify warm-up exercise description
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise description should be visible
    00 00 41.117
    check_circle Scenario: Verify warm-up duration
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise durations should be visible
    00 00 37.514
    check_circle Scenario: Verify warm-up calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise calories should be visible
    00 00 30.768
    check_circle Scenario: Verify warm-up intensity
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise intensity should be visible
    00 00 28.719
    check_circle Scenario: Verify "Main Workout" section is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" section should be visible
    00 00 43.098
    check_circle Scenario: Verify Main Workout exercise name
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise name should be visible
    00 00 37.908
    check_circle Scenario: Verify Main Workout exercise description
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise description should be visible
    00 00 33.169
    check_circle Scenario: Verify Main Workout duration
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise durations should be visible
    00 00 35.131
    check_circle Scenario: Verify Main Workout calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise calories should be visible
    00 00 30.936
    check_circle Scenario: Verify Main Workout intensity
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise intensity should be visible
    00 00 40.717
    check_circle Scenario: Verify "Cool Down" section is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" section should be visible
    00 00 40.156
    check_circle Scenario: Verify Cool Down exercise name
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise name should be visible
    00 00 32.381
    check_circle Scenario: Verify Cool Down exercise description
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise description should be visible
    00 00 33.490
    check_circle Scenario: Verify Cool Down duration
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise durations should be visible
    00 00 39.042
    check_circle Scenario: Verify Cool Down calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise calories should be visible
    00 00 31.480
    check_circle Scenario: Verify Cool Down intensity
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise intensity should be visible
    00 00 36.244
    check_circle Scenario: Verify the intensity value
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen Exercise intensity should low/medium/hard
    00 00 28.827
    check_circle Scenario: Verify total duration is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen total duration should be displayed
    00 00 33.389
    check_circle Scenario: Verify total duration matches the sum of individual workout durations
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen total duration should equal the sum of all individual durations
    00 00 42.856
    check_circle Scenario: Verify total calories matches the sum of individual workout calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen total calories should equal the sum of all individual calories
  • Premium User Exercise Schedule Functionality Jul 4, 2025 04:27:54 PM Fail
    check_circle cancel clear
    00 00 45.215
    check_circle Scenario: Verify "View Full Schedule" button is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "View Full Schedule" button is displayed on the right
    00 00 50.359
    check_circle Scenario: Verify navigation to "Today's Exercise Schedule" page
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "View Full Schedule" button
    • check_circleThen User is redirected to "Today's Exercise Schedule" page
    00 01 00.063
    check_circle Scenario: Verify "Warm Up" tab is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Warm Up" tab is visible
    00 00 56.536
    check_circle Scenario: Verify "Main Workout" tab is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Main Workout" tab is visible
    00 00 45.488
    check_circle Scenario: Verify "Cool Down" tab is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Cool Down" tab is visible
    00 00 38.704
    check_circle Scenario: Verify Exercise name is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Exercise name is displayed under "Warm Up" tab
    00 00 24.531
    check_circle Scenario: Verify Exercise name is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Exercise name is displayed under "Main Workout" tab
    00 00 47.540
    check_circle Scenario: Verify Exercise name is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Exercise name is displayed under "Cool Down" tab
    00 00 44.023
    check_circle Scenario: Verify Exercise description is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Description is shown below the Exercise name under "Warm Up"
    00 00 44.626
    check_circle Scenario: Verify Exercise description is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Description is shown below the Exercise name under "Main Workout"
    00 00 45.862
    check_circle Scenario: Verify Exercise description is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Description is shown below the Exercise name under "Cool Down"
    00 00 42.798
    check_circle Scenario: Verify duration is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Duration is displayed under "Warm Up" tab
    00 00 41.523
    check_circle Scenario: Verify calories are displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Calories are displayed under "Warm Up" tab
    00 00 32.971
    check_circle Scenario: Verify intensity level is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Intensity level is displayed under "Warm Up" tab
    00 00 32.622
    check_circle Scenario: Verify duration is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Duration is displayed under "Main Workout" tab
    00 00 46.917
    check_circle Scenario: Verify calories are displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Calories are displayed under "Main Workout" tab
    00 00 47.472
    check_circle Scenario: Verify intensity level is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Intensity level is displayed under "Main Workout" tab
    00 00 40.797
    check_circle Scenario: Verify duration is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Duration is displayed under "Cool Down" tab
    00 00 39.721
    check_circle Scenario: Verify calories are displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Calories are displayed under "Cool Down" tab
    00 00 37.620
    check_circle Scenario: Verify intensity level is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Intensity level is displayed under "Cool Down" tab
    00 00 45.202
    check_circle Scenario: Verify "Mark As Completed" button is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Mark As Completed" button is displayed for all three sections
    00 06 38.794
    cancel Scenario: Verify success dialog is shown after marking as completed
    @PremiumUser_Exercise
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 00 33.761
    check_circle Scenario: Verify button status changes to "Completed"
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Mark As Completed" button
    • check_circleThen Button changes to "Completed"
    00 00 38.499
    check_circle Scenario: Verify undo option is displayed after marking completed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Mark As Completed" button
    • check_circleThen Undo option is visible
    00 00 39.375
    check_circle Scenario: Verify button reverts back after undo
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks Undo after marking Exercise as completed
    • check_circleThen Button changes back to "Mark As Completed"
    00 00 23.164
    check_circle Scenario: Verify navigation to "View full schedule"
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen User should redirect to Exercise schedule
    00 00 38.032
    cancel Scenario: Verify page title is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • cancelThen User should see title "Today's Exercise Schedule"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_a_g_e_ _t_i_t_l_e_ _i_s_ _d_i_s_p_l_a_y_e_d_
    00 00 31.830
    check_circle Scenario: Verify "Back to Home" button is visible
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen User should see "Back to Home" button in Today's Exercise schedule page
    00 00 32.275
    check_circle Scenario: Verify "Warm Up" section is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" section should be visible
    00 00 33.365
    check_circle Scenario: Verify warm-up exercise name
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen Exercise name should be visible
    00 00 31.751
    check_circle Scenario: Verify warm-up exercise description
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise description should be visible
    00 00 45.161
    check_circle Scenario: Verify warm-up duration
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise durations should be visible
    00 00 39.482
    check_circle Scenario: Verify warm-up calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise calories should be visible
    00 00 37.050
    check_circle Scenario: Verify warm-up intensity
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise intensity should be visible
    00 00 36.536
    check_circle Scenario: Verify "Main Workout" section is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" section should be visible
    00 00 32.804
    check_circle Scenario: Verify Main Workout exercise name
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise name should be visible
    00 00 34.740
    check_circle Scenario: Verify Main Workout exercise description
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise description should be visible
    00 00 32.952
    check_circle Scenario: Verify Main Workout duration
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise durations should be visible
    00 00 33.535
    check_circle Scenario: Verify Main Workout calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise calories should be visible
    00 00 32.070
    check_circle Scenario: Verify Main Workout intensity
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise intensity should be visible
    00 00 37.238
    check_circle Scenario: Verify "Cool Down" section is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" section should be visible
    00 00 35.770
    check_circle Scenario: Verify Cool Down exercise name
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise name should be visible
    00 00 34.765
    check_circle Scenario: Verify Cool Down exercise description
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise description should be visible
    00 00 33.302
    check_circle Scenario: Verify Cool Down duration
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise durations should be visible
    00 00 40.573
    check_circle Scenario: Verify Cool Down calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise calories should be visible
    00 00 37.679
    check_circle Scenario: Verify Cool Down intensity
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise intensity should be visible
    00 00 37.931
    check_circle Scenario: Verify the intensity value
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen Exercise intensity should low/medium/hard
    00 00 36.849
    check_circle Scenario: Verify total duration is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen total duration should be displayed
    00 00 35.344
    check_circle Scenario: Verify total duration matches the sum of individual workout durations
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen total duration should equal the sum of all individual durations
    00 00 40.498
    check_circle Scenario: Verify total calories matches the sum of individual workout calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen total calories should equal the sum of all individual calories
  • Premium User Exercise Schedule Functionality Jul 4, 2025 04:29:01 PM Fail
    check_circle cancel clear
    00 00 39.979
    check_circle Scenario: Verify "View Full Schedule" button is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "View Full Schedule" button is displayed on the right
    00 00 35.189
    check_circle Scenario: Verify navigation to "Today's Exercise Schedule" page
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "View Full Schedule" button
    • check_circleThen User is redirected to "Today's Exercise Schedule" page
    00 00 42.783
    check_circle Scenario: Verify "Warm Up" tab is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Warm Up" tab is visible
    00 00 38.926
    check_circle Scenario: Verify "Main Workout" tab is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Main Workout" tab is visible
    00 00 39.433
    check_circle Scenario: Verify "Cool Down" tab is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Cool Down" tab is visible
    00 00 36.660
    check_circle Scenario: Verify Exercise name is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Exercise name is displayed under "Warm Up" tab
    00 00 39.460
    check_circle Scenario: Verify Exercise name is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Exercise name is displayed under "Main Workout" tab
    00 00 50.354
    check_circle Scenario: Verify Exercise name is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Exercise name is displayed under "Cool Down" tab
    00 00 47.325
    check_circle Scenario: Verify Exercise description is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Description is shown below the Exercise name under "Warm Up"
    00 00 54.653
    check_circle Scenario: Verify Exercise description is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Description is shown below the Exercise name under "Main Workout"
    00 00 50.576
    check_circle Scenario: Verify Exercise description is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Description is shown below the Exercise name under "Cool Down"
    00 00 49.483
    check_circle Scenario: Verify duration is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Duration is displayed under "Warm Up" tab
    00 00 46.201
    check_circle Scenario: Verify calories are displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Calories are displayed under "Warm Up" tab
    00 00 43.273
    check_circle Scenario: Verify intensity level is displayed under "Warm Up" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Intensity level is displayed under "Warm Up" tab
    00 00 42.350
    check_circle Scenario: Verify duration is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Duration is displayed under "Main Workout" tab
    00 00 24.049
    check_circle Scenario: Verify calories are displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Calories are displayed under "Main Workout" tab
    00 00 30.354
    check_circle Scenario: Verify intensity level is displayed under "Main Workout" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Intensity level is displayed under "Main Workout" tab
    00 00 41.939
    check_circle Scenario: Verify duration is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Duration is displayed under "Cool Down" tab
    00 00 26.486
    check_circle Scenario: Verify calories are displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Calories are displayed under "Cool Down" tab
    00 00 39.511
    check_circle Scenario: Verify intensity level is displayed under "Cool Down" tab
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen Intensity level is displayed under "Cool Down" tab
    00 00 37.160
    check_circle Scenario: Verify "Mark As Completed" button is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Exercise" option from the side panel
    • check_circleThen "Mark As Completed" button is displayed for all three sections
    00 00 40.710
    check_circle Scenario: Verify success dialog is shown after marking as completed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Mark As Completed" button
    • check_circleThen Success dialog is shown
    00 00 37.626
    check_circle Scenario: Verify button status changes to "Completed"
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Mark As Completed" button
    • check_circleThen Button changes to "Completed"
    00 00 35.418
    check_circle Scenario: Verify undo option is displayed after marking completed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User clicks the "Mark As Completed" button
    • check_circleThen Undo option is visible
    00 00 36.374
    check_circle Scenario: Verify button reverts back after undo
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks Undo after marking Exercise as completed
    • check_circleThen Button changes back to "Mark As Completed"
    00 00 30.738
    check_circle Scenario: Verify navigation to "View full schedule"
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen User should redirect to Exercise schedule
    00 00 43.111
    cancel Scenario: Verify page title is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • cancelThen User should see title "Today's Exercise Schedule"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_a_g_e_ _t_i_t_l_e_ _i_s_ _d_i_s_p_l_a_y_e_d_
    00 00 41.734
    check_circle Scenario: Verify "Back to Home" button is visible
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen User should see "Back to Home" button in Today's Exercise schedule page
    00 00 33.473
    check_circle Scenario: Verify "Warm Up" section is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" section should be visible
    00 00 40.811
    check_circle Scenario: Verify warm-up exercise name
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen Exercise name should be visible
    00 00 37.040
    check_circle Scenario: Verify warm-up exercise description
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise description should be visible
    00 00 25.714
    check_circle Scenario: Verify warm-up duration
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise durations should be visible
    00 00 32.757
    check_circle Scenario: Verify warm-up calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise calories should be visible
    00 00 42.442
    check_circle Scenario: Verify warm-up intensity
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Warm Up" Exercise intensity should be visible
    00 00 39.424
    check_circle Scenario: Verify "Main Workout" section is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" section should be visible
    00 00 38.851
    check_circle Scenario: Verify Main Workout exercise name
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise name should be visible
    00 00 41.865
    check_circle Scenario: Verify Main Workout exercise description
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise description should be visible
    00 00 34.736
    check_circle Scenario: Verify Main Workout duration
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise durations should be visible
    00 00 36.512
    check_circle Scenario: Verify Main Workout calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise calories should be visible
    00 00 35.861
    check_circle Scenario: Verify Main Workout intensity
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Main Workout" Exercise intensity should be visible
    00 00 26.204
    check_circle Scenario: Verify "Cool Down" section is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" section should be visible
    00 00 39.562
    check_circle Scenario: Verify Cool Down exercise name
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise name should be visible
    00 00 48.522
    check_circle Scenario: Verify Cool Down exercise description
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise description should be visible
    00 00 41.111
    check_circle Scenario: Verify Cool Down duration
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise durations should be visible
    00 00 40.887
    check_circle Scenario: Verify Cool Down calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise calories should be visible
    00 01 10.581
    check_circle Scenario: Verify Cool Down intensity
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen "Cool Down" Exercise intensity should be visible
    00 01 03.860
    check_circle Scenario: Verify the intensity value
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen Exercise intensity should low/medium/hard
    00 00 58.547
    check_circle Scenario: Verify total duration is displayed
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen total duration should be displayed
    00 00 59.773
    check_circle Scenario: Verify total duration matches the sum of individual workout durations
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen total duration should equal the sum of all individual durations
    00 01 05.465
    check_circle Scenario: Verify total calories matches the sum of individual workout calories
    @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is in the Exercise section
    • check_circleWhen User clicks "view full schedule"
    • check_circleThen total calories should equal the sum of all individual calories
  • Home Page Validation for Registered Premium Account User Jul 4, 2025 04:32:28 PM Fail
    check_circle cancel clear
    00 01 03.958
    check_circle Scenario: Verify order of text in navigation bar
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see the navigation bar displaying items in the order: Home, Logbook, Dashboard, Education
    00 01 02.850
    cancel Scenario: Verify the presence of animation in challenge yourself button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _a_n_i_m_a_t_i_o_n_ _i_n_ _c_h_a_l_l_e_n_g_e_ _y_o_u_r_s_e_l_f_ _b_u_t_t_o_n_
    00 02 42.725
    cancel Scenario: Verify the duration of animation
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 19.452
    cancel Scenario: Verify the presence of Challenge yourself today button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 00.739
    cancel Scenario: Verify the presence of gender image in the grid
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 27.308
    check_circle Scenario: Verify the presence of emoji on top right of gender image
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see an emoji displayed on the top-right corner of the gender image
    00 01 25.547
    check_circle Scenario: Verify the label for gender image
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see label "Mood:" below the gender image
    00 01 24.749
    check_circle Scenario: Verify the presence of log button
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see log button under gender image
    00 02 01.430
    check_circle Scenario: Verify display mood text based on emoji
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see mood text based on the emoji
    00 03 31.674
    cancel Scenario: Verify the presence of Weekly plan button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 00.373
    cancel Scenario: Verify the presence of "Record New Data" in the bottom
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 20.770
    check_circle Scenario: Verify the presence of 4 button option below Record New Data
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see 4 button options
    00 02 13.822
    check_circle Scenario: Verify the first button text "Blood Glucose"
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see text Blood Glucose
    00 03 47.119
    cancel Scenario: Verify the second button text "Physical Activity"
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 07.682
    cancel Scenario: Verify the third button text "Food Intake"
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 04.418
    cancel Scenario: Verify the fourth button text "Medication"
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 10.370
    check_circle Scenario: Verify icon for Blood Glucose
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see Activity icon in Blood Glucose
    00 04 00.009
    cancel Scenario: Verify icon for Physical Activity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 05 00.593
    cancel Scenario: Verify icon for Food Intake
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 39.100
    cancel Scenario: Verify icon for Medication
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Home Page Validation for Registered Premium Account User Jul 4, 2025 04:32:44 PM Fail
    check_circle cancel clear
    00 03 14.795
    cancel Scenario: Verify order of text in navigation bar
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 27.021
    cancel Scenario: Verify the presence of animation in challenge yourself button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 03.384
    cancel Scenario: Verify the duration of animation
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 11.480
    check_circle Scenario: Verify the presence of Challenge yourself today button
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see a "Challenge yourself today!" button
    00 02 44.460
    check_circle Scenario: Verify the presence of gender image in the grid
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see a gender-specific image based on the gender selected during onboarding
    00 02 06.513
    check_circle Scenario: Verify the presence of emoji on top right of gender image
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see an emoji displayed on the top-right corner of the gender image
    00 02 41.842
    cancel Scenario: Verify the label for gender image
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 05.529
    cancel Scenario: Verify the presence of log button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 52.249
    check_circle Scenario: Verify display mood text based on emoji
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see mood text based on the emoji
    00 07 09.588
    cancel Scenario: Verify the presence of Weekly plan button
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 07.106
    cancel Scenario: Verify the presence of "Record New Data" in the bottom
    @PremiumUser_Exercise
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 04.494
    cancel Scenario: Verify the presence of 4 button option below Record New Data
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 02.850
    cancel Scenario: Verify the first button text "Blood Glucose"
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 24.227
    cancel Scenario: Verify the second button text "Physical Activity"
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 23.766
    cancel Scenario: Verify the third button text "Food Intake"
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 32.428
    cancel Scenario: Verify the fourth button text "Medication"
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 04.841
    cancel Scenario: Verify icon for Blood Glucose
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _i_c_o_n_ _f_o_r_ _B_l_o_o_d_ _G_l_u_c_o_s_e_
    00 03 48.448
    cancel Scenario: Verify icon for Physical Activity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 53.547
    cancel Scenario: Verify icon for Food Intake
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 51.935
    cancel Scenario: Verify icon for Medication
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Home Page Validation for Registered Premium Account User Jul 4, 2025 04:33:05 PM Fail
    check_circle cancel clear
    00 02 03.204
    check_circle Scenario: Verify order of text in navigation bar
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see the navigation bar displaying items in the order: Home, Logbook, Dashboard, Education
    00 02 01.320
    check_circle Scenario: Verify the presence of animation in challenge yourself button
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see flashing challenge yourself button
    00 04 02.508
    cancel Scenario: Verify the presence of Challenge yourself today button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 03.658
    cancel Scenario: Verify the duration of animation
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 12.927
    check_circle Scenario: Verify the presence of gender image in the grid
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see a gender-specific image based on the gender selected during onboarding
    00 11 32.035
    cancel Scenario: Verify the presence of emoji on top right of gender image
    @PremiumUser_Exercise
    • cancelGiven the user is in password auth page
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 24.688
    check_circle Scenario: Verify the label for gender image
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see label "Mood:" below the gender image
    00 01 55.661
    check_circle Scenario: Verify the presence of log button
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see log button under gender image
    00 03 31.030
    cancel Scenario: Verify display mood text based on emoji
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 37.812
    cancel Scenario: Verify the presence of Weekly plan button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 08.002
    cancel Scenario: Verify the presence of "Record New Data" in the bottom
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 06.632
    cancel Scenario: Verify the presence of 4 button option below Record New Data
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 14.318
    cancel Scenario: Verify the first button text "Blood Glucose"
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 16.494
    check_circle Scenario: Verify the second button text "Physical Activity"
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleThen the user should see text Physical Activity
    00 03 21.426
    cancel Scenario: Verify the third button text "Food Intake"
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 26.066
    cancel Scenario: Verify icon for Blood Glucose
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 29.657
    cancel Scenario: Verify the fourth button text "Medication"
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 14.949
    cancel Scenario: Verify icon for Physical Activity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 06.948
    cancel Scenario: Verify icon for Food Intake
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 09.097
    cancel Scenario: Verify icon for Medication
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Premium User Logbook Functionality for Blood Glucose Jul 4, 2025 04:37:04 PM Fail
    check_circle cancel clear
    00 01 39.728
    check_circle Scenario: Verify presence of Blood Glucose Tracker section
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see Blood Glucose Tracker
    00 02 07.544
    cancel Scenario: Verify title of Blood Glucose tracker section
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • cancelThen User should see title "Blood Glucose Tracker"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_i_t_l_e_ _o_f_ _B_l_o_o_d_ _G_l_u_c_o_s_e_ _t_r_a_c_k_e_r_ _s_e_c_t_i_o_n_
    00 01 02.861
    check_circle Scenario: Verify colour codes for Fasting
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Fasting" displayed in purple
    00 01 28.359
    check_circle Scenario: Verify Fasting glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the range for "Fasting" be "70-100 mg/dL"
    00 01 17.937
    check_circle Scenario: Verify colour codes for Pre-Meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Pre-Meal" displayed in green
    00 07 30.293
    cancel Scenario: Verify pre-meal glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 32.613
    cancel Scenario: Verify colour codes for Post-Meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 14.080
    cancel Scenario: Verify Post-meal glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 16.836
    check_circle Scenario: Verify colour codes for Bedtime
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Bedtime" displayed in red
    00 01 15.866
    check_circle Scenario: Verify bedtime glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the range for "Bedtime" be "100-140 mg/dL"
    00 00 53.293
    check_circle Scenario: Verify last 7 days are displayed on X-axis
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the X-axis display the last 7 days ending today
    00 01 09.394
    check_circle Scenario: Verify Y-axis starts at 70 in glucose chart
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see Y-axis minimum value 70
    00 00 45.875
    check_circle Scenario: Verify Y-axis ends at 180 in glucose chart
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see X-axis Maximum value 180
  • Premium User Logbook Functionality for Blood Glucose Jul 4, 2025 04:39:07 PM Fail
    check_circle cancel clear
    00 07 19.463
    cancel Scenario: Verify presence of Blood Glucose Tracker section
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 01.211
    cancel Scenario: Verify title of Blood Glucose tracker section
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 00 44.931
    check_circle Scenario: Verify colour codes for Fasting
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Fasting" displayed in purple
    00 00 44.467
    check_circle Scenario: Verify Fasting glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the range for "Fasting" be "70-100 mg/dL"
    00 00 44.866
    check_circle Scenario: Verify colour codes for Pre-Meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Pre-Meal" displayed in green
    00 00 41.134
    check_circle Scenario: Verify pre-meal glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the range for "pre meal" be "70-130 mg/dL"
    00 00 34.619
    check_circle Scenario: Verify colour codes for Post-Meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Post-Meal" displayed in yellow
    00 00 22.892
    check_circle Scenario: Verify Post-meal glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the range for "post meal" be "<180 mg/dL"
    00 00 24.355
    check_circle Scenario: Verify colour codes for Bedtime
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Bedtime" displayed in red
    00 00 23.032
    check_circle Scenario: Verify bedtime glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the range for "Bedtime" be "100-140 mg/dL"
    00 00 24.507
    check_circle Scenario: Verify last 7 days are displayed on X-axis
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the X-axis display the last 7 days ending today
    00 00 23.796
    check_circle Scenario: Verify Y-axis starts at 70 in glucose chart
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see Y-axis minimum value 70
    00 00 29.790
    check_circle Scenario: Verify Y-axis ends at 180 in glucose chart
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see X-axis Maximum value 180
  • Premium User Logbook Functionality for Blood Glucose Jul 4, 2025 04:39:10 PM Fail
    check_circle cancel clear
    00 07 11.898
    cancel Scenario: Verify presence of Blood Glucose Tracker section
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 09.222
    cancel Scenario: Verify title of Blood Glucose tracker section
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 08.833
    check_circle Scenario: Verify colour codes for Fasting
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Fasting" displayed in purple
    00 06 47.672
    cancel Scenario: Verify Fasting glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 00 45.992
    check_circle Scenario: Verify colour codes for Pre-Meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Pre-Meal" displayed in green
    00 00 42.907
    check_circle Scenario: Verify pre-meal glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the range for "pre meal" be "70-130 mg/dL"
    00 00 37.713
    check_circle Scenario: Verify colour codes for Post-Meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Post-Meal" displayed in yellow
    00 00 33.631
    check_circle Scenario: Verify Post-meal glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the range for "post meal" be "<180 mg/dL"
    00 00 26.285
    check_circle Scenario: Verify colour codes for Bedtime
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "Bedtime" displayed in red
    00 00 28.666
    check_circle Scenario: Verify bedtime glucose type range displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the range for "Bedtime" be "100-140 mg/dL"
    00 00 21.880
    check_circle Scenario: Verify last 7 days are displayed on X-axis
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the X-axis display the last 7 days ending today
    00 00 30.934
    check_circle Scenario: Verify Y-axis starts at 70 in glucose chart
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see Y-axis minimum value 70
    00 00 40.864
    check_circle Scenario: Verify Y-axis ends at 180 in glucose chart
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see X-axis Maximum value 180
  • Premium User Logbook Functionality for Log Review Jul 4, 2025 04:40:40 PM Pass
    check_circle cancel clear
    00 00 51.956
    check_circle Scenario: Verify the Title of Log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Log Review"
    00 00 42.163
    check_circle Scenario: Verify table header in log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see table header "Date","Blood Glucose","Nutrition","Activity",Medication"
    00 00 33.364
    check_circle Scenario: Verify log review displays last 7 days of date entries including today
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see date of last seven days including today
    00 00 34.342
    check_circle Scenario: Verify the display of date format
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date format as "MMM dd, yyyy"
    00 00 29.868
    check_circle Scenario: Verify the order of date
    @PremiumUser_Exercise @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date ordered in descending order for last 7 days including today
    00 00 31.775
    check_circle Scenario: Verify the blood glucose value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any blood glucose value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under blood glucose
    00 00 25.834
    check_circle Scenario: Verify the nutrient value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any nutrition value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Nutrition value
    00 00 25.590
    check_circle Scenario: Verify the physical activity value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Physical activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Activity
    00 00 22.303
    check_circle Scenario: Verify the entries of Medication in log review section if there is no value
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Medication dosage in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Medication
    00 00 22.865
    check_circle Scenario: Verify the blood glucose entries in log review section if there is log
    @PremiumUser_Exercise @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log blood glucose value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Blood glucose
    00 00 19.409
    check_circle Scenario: Verify the nutrient value entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Nutrient value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Nutrient value
    00 00 29.096
    check_circle Scenario: Verify the physical activity entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Physical Activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under physical activity
    00 00 41.003
    check_circle Scenario: Verify the medication value in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Medication dosage in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those under Medication Dosage
  • Premium User Logbook Functionality for Log Review Jul 4, 2025 04:42:04 PM Pass
    check_circle cancel clear
    00 00 30.318
    check_circle Scenario: Verify the Title of Log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Log Review"
    00 00 32.009
    check_circle Scenario: Verify table header in log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see table header "Date","Blood Glucose","Nutrition","Activity",Medication"
    00 00 31.547
    check_circle Scenario: Verify log review displays last 7 days of date entries including today
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see date of last seven days including today
    00 00 39.169
    check_circle Scenario: Verify the display of date format
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date format as "MMM dd, yyyy"
    00 00 39.954
    check_circle Scenario: Verify the order of date
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date ordered in descending order for last 7 days including today
    00 00 42.949
    check_circle Scenario: Verify the blood glucose value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any blood glucose value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under blood glucose
    00 00 46.647
    check_circle Scenario: Verify the nutrient value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any nutrition value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Nutrition value
    00 00 46.453
    check_circle Scenario: Verify the physical activity value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Physical activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Activity
    00 00 40.488
    check_circle Scenario: Verify the entries of Medication in log review section if there is no value
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Medication dosage in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Medication
    00 00 42.099
    check_circle Scenario: Verify the blood glucose entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log blood glucose value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Blood glucose
    00 00 48.295
    check_circle Scenario: Verify the nutrient value entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Nutrient value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Nutrient value
    00 00 49.555
    check_circle Scenario: Verify the physical activity entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Physical Activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under physical activity
    00 00 44.328
    check_circle Scenario: Verify the medication value in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Medication dosage in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those under Medication Dosage
  • Premium User Logbook Functionality for Log Review Jul 4, 2025 04:42:17 PM Pass
    check_circle cancel clear
    00 00 34.133
    check_circle Scenario: Verify the Title of Log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Log Review"
    00 00 36.511
    check_circle Scenario: Verify table header in log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see table header "Date","Blood Glucose","Nutrition","Activity",Medication"
    00 00 39.904
    check_circle Scenario: Verify log review displays last 7 days of date entries including today
    @PremiumUser_Exercise @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see date of last seven days including today
    00 00 41.059
    check_circle Scenario: Verify the display of date format
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date format as "MMM dd, yyyy"
    00 00 41.037
    check_circle Scenario: Verify the order of date
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date ordered in descending order for last 7 days including today
    00 00 41.995
    check_circle Scenario: Verify the blood glucose value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any blood glucose value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under blood glucose
    00 00 54.391
    check_circle Scenario: Verify the nutrient value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any nutrition value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Nutrition value
    00 00 42.949
    check_circle Scenario: Verify the physical activity value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Physical activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Activity
    00 00 46.447
    check_circle Scenario: Verify the entries of Medication in log review section if there is no value
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Medication dosage in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Medication
    00 00 49.798
    check_circle Scenario: Verify the blood glucose entries in log review section if there is log
    @PremiumUser_Exercise @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log blood glucose value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Blood glucose
    00 00 48.422
    check_circle Scenario: Verify the nutrient value entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Nutrient value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Nutrient value
    00 00 44.543
    check_circle Scenario: Verify the physical activity entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Physical Activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under physical activity
    00 00 41.968
    check_circle Scenario: Verify the medication value in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Medication dosage in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those under Medication Dosage
  • Premium User Logbook Functionality for Log Review Jul 4, 2025 04:42:17 PM Pass
    check_circle cancel clear
    00 00 36.756
    check_circle Scenario: Verify the Title of Log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Log Review"
    00 00 35.927
    check_circle Scenario: Verify table header in log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see table header "Date","Blood Glucose","Nutrition","Activity",Medication"
    00 00 38.907
    check_circle Scenario: Verify log review displays last 7 days of date entries including today
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see date of last seven days including today
    00 00 38.803
    check_circle Scenario: Verify the display of date format
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date format as "MMM dd, yyyy"
    00 00 52.910
    check_circle Scenario: Verify the order of date
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date ordered in descending order for last 7 days including today
    00 00 47.314
    check_circle Scenario: Verify the blood glucose value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any blood glucose value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under blood glucose
    00 00 41.352
    check_circle Scenario: Verify the nutrient value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any nutrition value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Nutrition value
    00 00 54.872
    check_circle Scenario: Verify the physical activity value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Physical activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Activity
    00 00 51.186
    check_circle Scenario: Verify the entries of Medication in log review section if there is no value
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Medication dosage in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Medication
    00 00 52.708
    check_circle Scenario: Verify the blood glucose entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log blood glucose value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Blood glucose
    00 00 51.793
    check_circle Scenario: Verify the nutrient value entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Nutrient value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Nutrient value
    00 00 44.404
    check_circle Scenario: Verify the physical activity entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Physical Activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under physical activity
    00 00 45.084
    check_circle Scenario: Verify the medication value in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Medication dosage in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those under Medication Dosage
  • Premium User Logbook Functionality for Log Review Jul 4, 2025 04:43:19 PM Pass
    check_circle cancel clear
    00 00 36.431
    check_circle Scenario: Verify the Title of Log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Log Review"
    00 00 42.272
    check_circle Scenario: Verify table header in log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see table header "Date","Blood Glucose","Nutrition","Activity",Medication"
    00 00 45.343
    check_circle Scenario: Verify log review displays last 7 days of date entries including today
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see date of last seven days including today
    00 00 40.773
    check_circle Scenario: Verify the display of date format
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date format as "MMM dd, yyyy"
    00 00 37.662
    check_circle Scenario: Verify the order of date
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date ordered in descending order for last 7 days including today
    00 00 35.990
    check_circle Scenario: Verify the blood glucose value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any blood glucose value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under blood glucose
    00 00 41.076
    check_circle Scenario: Verify the nutrient value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any nutrition value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Nutrition value
    00 00 38.261
    check_circle Scenario: Verify the physical activity value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Physical activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Activity
    00 00 37.639
    check_circle Scenario: Verify the entries of Medication in log review section if there is no value
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Medication dosage in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Medication
    00 00 32.040
    check_circle Scenario: Verify the blood glucose entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log blood glucose value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Blood glucose
    00 00 35.175
    check_circle Scenario: Verify the nutrient value entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Nutrient value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Nutrient value
    00 00 38.727
    check_circle Scenario: Verify the physical activity entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Physical Activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under physical activity
    00 00 41.377
    check_circle Scenario: Verify the medication value in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Medication dosage in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those under Medication Dosage
  • Premium User Logbook Functionality for Medical Dosage Jul 4, 2025 04:43:35 PM Pass
    check_circle cancel clear
    00 00 48.046
    check_circle Scenario: Verify the presence of Medical Dosage section
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the section Medical Dosage
    00 00 41.093
    check_circle Scenario: Verify the title "Medical dosage"
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Medical Dosage"
    00 00 50.206
    check_circle Scenario: Verify the icon beside medical dosage
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the icon on left side of title
    00 00 37.595
    check_circle Scenario: Verify the Y-axis has text "Number of Doses"
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the text "Number of Doses"on Y-axis
    00 00 38.349
    check_circle Scenario: Verify display empty chart when no medication is scheduled
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see no bars in the chart
    00 00 40.155
    check_circle Scenario: Verify Total scheduled will display 0 doses, if no medication is scheduled
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "0 doses" value in the Total scheduled statistics
    00 00 33.109
    check_circle Scenario: Verify Doses Taken will display 0 doses , if no medication is displayed
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "0 doses" value in the Doses taken statistics
    00 00 38.082
    check_circle Scenario: Verify Doses Missed will display 0 doses, if no Medication is displayed
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "0 doses" value in the Doses Missed statistics
    00 00 38.533
    check_circle Scenario: Verify the colour of Total Scheduled text
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see purple colour text
    00 00 33.135
    check_circle Scenario: Verify the colour of Doses Taken text
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see green colour text
    00 00 38.705
    check_circle Scenario: Verify the colour of Doses Missed text
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see yellow colour text
    00 00 40.766
    check_circle Scenario: verify green colour bar is displayed for doses taken on one week schedule
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has taken the scheduled dose for a day
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see green colour bar for that day
    00 00 33.358
    check_circle Scenario: Verify red colour bard is displayed for doses missed on one week schedule
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has taken the scheduled dose for a day
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see red colour bar for that day
  • Premium User Logbook Functionality for Log Review Jul 4, 2025 04:43:36 PM Pass
    check_circle cancel clear
    00 00 43.064
    check_circle Scenario: Verify the Title of Log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Log Review"
    00 00 38.775
    check_circle Scenario: Verify table header in log review section
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see table header "Date","Blood Glucose","Nutrition","Activity",Medication"
    00 00 37.026
    check_circle Scenario: Verify log review displays last 7 days of date entries including today
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see date of last seven days including today
    00 00 39.841
    check_circle Scenario: Verify the display of date format
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date format as "MMM dd, yyyy"
    00 00 39.233
    check_circle Scenario: Verify the order of date
    @PremiumUser_Exercise @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the date ordered in descending order for last 7 days including today
    00 00 37.504
    check_circle Scenario: Verify the blood glucose value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any blood glucose value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under blood glucose
    00 00 36.241
    check_circle Scenario: Verify the nutrient value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any nutrition value in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Nutrition value
    00 00 38.826
    check_circle Scenario: Verify the physical activity value in log review section if there is no log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Physical activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Activity
    00 00 42.201
    check_circle Scenario: Verify the entries of Medication in log review section if there is no value
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User have not log any Medication dosage in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see hyphen "-" for all the days under Medication
    00 00 34.740
    check_circle Scenario: Verify the blood glucose entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log blood glucose value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Blood glucose
    00 00 38.000
    check_circle Scenario: Verify the nutrient value entries in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Nutrient value in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under Nutrient value
    00 00 36.603
    check_circle Scenario: Verify the physical activity entries in log review section if there is log
    @PremiumUser_Exercise @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Physical Activity in home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those days under physical activity
    00 00 37.723
    check_circle Scenario: Verify the medication value in log review section if there is log
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User log Medication dosage in Home page
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see logged value for those under Medication Dosage
  • Premium User Logbook Functionality for Medical Dosage Jul 4, 2025 04:44:29 PM Pass
    check_circle cancel clear
    00 00 42.819
    check_circle Scenario: Verify the presence of Medical Dosage section
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the section Medical Dosage
    00 00 38.256
    check_circle Scenario: Verify the title "Medical dosage"
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Medical Dosage"
    00 00 43.492
    check_circle Scenario: Verify the icon beside medical dosage
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the icon on left side of title
    00 00 33.347
    check_circle Scenario: Verify the Y-axis has text "Number of Doses"
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the text "Number of Doses"on Y-axis
    00 00 38.338
    check_circle Scenario: Verify display empty chart when no medication is scheduled
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see no bars in the chart
    00 00 38.941
    check_circle Scenario: Verify Total scheduled will display 0 doses, if no medication is scheduled
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "0 doses" value in the Total scheduled statistics
    00 00 30.769
    check_circle Scenario: Verify Doses Taken will display 0 doses , if no medication is displayed
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "0 doses" value in the Doses taken statistics
    00 00 41.190
    check_circle Scenario: Verify Doses Missed will display 0 doses, if no Medication is displayed
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "0 doses" value in the Doses Missed statistics
    00 00 37.910
    check_circle Scenario: Verify the colour of Total Scheduled text
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see purple colour text
    00 00 42.335
    check_circle Scenario: Verify the colour of Doses Taken text
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see green colour text
    00 00 35.396
    check_circle Scenario: Verify the colour of Doses Missed text
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see yellow colour text
    00 00 33.989
    check_circle Scenario: verify green colour bar is displayed for doses taken on one week schedule
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has taken the scheduled dose for a day
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see green colour bar for that day
    00 00 41.282
    check_circle Scenario: Verify red colour bard is displayed for doses missed on one week schedule
    @PremiumUser_LogbookMedicalDosage @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has taken the scheduled dose for a day
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see red colour bar for that day
  • Premium User Logbook Functionality for Medical Dosage Jul 4, 2025 04:44:38 PM Pass
    check_circle cancel clear
    00 00 39.135
    check_circle Scenario: Verify the presence of Medical Dosage section
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the section Medical Dosage
    00 00 37.996
    check_circle Scenario: Verify the title "Medical dosage"
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Medical Dosage"
    00 00 36.450
    check_circle Scenario: Verify the icon beside medical dosage
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the icon on left side of title
    00 00 31.656
    check_circle Scenario: Verify the Y-axis has text "Number of Doses"
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the text "Number of Doses"on Y-axis
    00 00 30.112
    check_circle Scenario: Verify display empty chart when no medication is scheduled
    @PremiumUser_LogbookMedicalDosage @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see no bars in the chart
    00 00 32.899
    check_circle Scenario: Verify Total scheduled will display 0 doses, if no medication is scheduled
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "0 doses" value in the Total scheduled statistics
    00 00 31.697
    check_circle Scenario: Verify Doses Taken will display 0 doses , if no medication is displayed
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "0 doses" value in the Doses taken statistics
    00 00 34.555
    check_circle Scenario: Verify Doses Missed will display 0 doses, if no Medication is displayed
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "0 doses" value in the Doses Missed statistics
    00 00 35.125
    check_circle Scenario: Verify the colour of Total Scheduled text
    @PremiumUser_LogbookMedicalDosage @PremiumUser_Exercise
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see purple colour text
    00 00 33.352
    check_circle Scenario: Verify the colour of Doses Taken text
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see green colour text
    00 00 38.083
    check_circle Scenario: Verify the colour of Doses Missed text
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has not scheduled any medication for the week
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see yellow colour text
    00 00 32.925
    check_circle Scenario: verify green colour bar is displayed for doses taken on one week schedule
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has taken the scheduled dose for a day
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see green colour bar for that day
    00 00 34.517
    check_circle Scenario: Verify red colour bard is displayed for doses missed on one week schedule
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is Logged into the app
    • check_circleGiven User has taken the scheduled dose for a day
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see red colour bar for that day
  • Premium User Logbook Functionality for Physical Activity Jul 4, 2025 04:44:42 PM Pass
    check_circle cancel clear
    00 00 35.668
    check_circle Scenario: Verify the presence of Physical activity section
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "physical Activity" section
    00 00 33.746
    check_circle Scenario: Verify the title of physical activity section
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Physical Activity"
    00 00 35.737
    check_circle Scenario: Verify the presence of icons beside title physical activity
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the icons on left side of title
    00 00 32.210
    check_circle Scenario: Verify last 7 days are displayed on X-axis
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the X-axis display the last 7 days ending today
    00 00 46.862
    check_circle Scenario: Verify the alignment of statistic card "Total calories","Daily Average","Peak day"
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see exactly 3 statistic cards displayed horizontally
    00 00 41.655
    check_circle Scenario: Verify the text colour of total calories
    @PremiumUser_LogbookPhysicalActivity @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should the text in purple colour
    00 00 32.311
    check_circle Scenario: Verify the text colour of daily average
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see text in Orange color
    00 00 33.778
    check_circle Scenario: verify the text colour of peak day
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see text in Red color
    00 00 33.133
    check_circle Scenario: Verify Y-axis has text calories
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see y-axis clearly labeled with the text "Calories"
    00 00 35.675
    check_circle Scenario: Verify display of empty chart for no activity log
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see no bars in the chart
    00 00 31.969
    check_circle Scenario: verify the total calories value for no activity log
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see total calories has "0 cal" value
    00 00 35.892
    check_circle Scenario: Verify the daily average value for no activity log
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see Daily average has "0 cal" value
    00 00 35.482
    check_circle Scenario: Verify the peak day value for no activity log
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see no value
    00 00 31.441
    check_circle Scenario: Verify the display of bars if there is activity log in home page
    @PremiumUser_LogbookPhysicalActivity @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen user should see the bars displayed only for days with logged activities
  • Premium User Logbook Functionality for Physical Activity Jul 4, 2025 04:45:35 PM Pass
    check_circle cancel clear
    00 00 38.431
    check_circle Scenario: Verify the presence of Physical activity section
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "physical Activity" section
    00 00 32.421
    check_circle Scenario: Verify the title of physical activity section
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Physical Activity"
    00 00 35.334
    check_circle Scenario: Verify the presence of icons beside title physical activity
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the icons on left side of title
    00 00 34.248
    check_circle Scenario: Verify last 7 days are displayed on X-axis
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the X-axis display the last 7 days ending today
    00 00 34.165
    check_circle Scenario: Verify the alignment of statistic card "Total calories","Daily Average","Peak day"
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see exactly 3 statistic cards displayed horizontally
    00 00 35.005
    check_circle Scenario: Verify the text colour of total calories
    @PremiumUser_LogbookPhysicalActivity @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should the text in purple colour
    00 00 31.977
    check_circle Scenario: Verify the text colour of daily average
    @PremiumUser_LogbookPhysicalActivity @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see text in Orange color
    00 00 41.010
    check_circle Scenario: verify the text colour of peak day
    @PremiumUser_Exercise @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see text in Red color
    00 00 31.969
    check_circle Scenario: Verify Y-axis has text calories
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see y-axis clearly labeled with the text "Calories"
    00 00 32.499
    check_circle Scenario: Verify display of empty chart for no activity log
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see no bars in the chart
    00 00 47.167
    check_circle Scenario: verify the total calories value for no activity log
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see total calories has "0 cal" value
    00 00 55.252
    check_circle Scenario: Verify the daily average value for no activity log
    @PremiumUser_LogbookBloodGlucoseTracker @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see Daily average has "0 cal" value
    00 00 53.247
    check_circle Scenario: Verify the peak day value for no activity log
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see no value
    00 00 39.198
    check_circle Scenario: Verify the display of bars if there is activity log in home page
    @PremiumUser_LogbookPhysicalActivity @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen user should see the bars displayed only for days with logged activities
  • Premium User Logbook Functionality for Physical Activity Jul 4, 2025 04:45:37 PM Pass
    check_circle cancel clear
    00 00 34.801
    check_circle Scenario: Verify the presence of Physical activity section
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see "physical Activity" section
    00 00 32.419
    check_circle Scenario: Verify the title of physical activity section
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the title "Physical Activity"
    00 00 39.903
    check_circle Scenario: Verify the presence of icons beside title physical activity
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the icons on left side of title
    00 00 36.585
    check_circle Scenario: Verify last 7 days are displayed on X-axis
    @PremiumUser_LogbookPhysicalActivity @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see the X-axis display the last 7 days ending today
    00 00 41.858
    check_circle Scenario: Verify the alignment of statistic card "Total calories","Daily Average","Peak day"
    @PremiumUser_Exercise @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see exactly 3 statistic cards displayed horizontally
    00 00 35.125
    check_circle Scenario: Verify the text colour of total calories
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should the text in purple colour
    00 00 34.072
    check_circle Scenario: Verify the text colour of daily average
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see text in Orange color
    00 00 33.767
    check_circle Scenario: verify the text colour of peak day
    @PremiumUser_LogbookPhysicalActivity @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see text in Red color
    00 00 41.878
    check_circle Scenario: Verify Y-axis has text calories
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see y-axis clearly labeled with the text "Calories"
    00 00 51.201
    check_circle Scenario: Verify display of empty chart for no activity log
    @PremiumUser_LogbookBloodGlucoseTracker @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see no bars in the chart
    00 00 48.402
    check_circle Scenario: verify the total calories value for no activity log
    @PremiumUser_LogbookMedicalDosage @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see total calories has "0 cal" value
    00 00 43.353
    check_circle Scenario: Verify the daily average value for no activity log
    @PremiumUser_LogbookPhysicalActivity @PremiumUser_LogbookLogReview
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see Daily average has "0 cal" value
    00 00 52.213
    check_circle Scenario: Verify the peak day value for no activity log
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen User should see no value
    00 00 59.154
    check_circle Scenario: Verify the display of bars if there is activity log in home page
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is Logged into the app
    • check_circleGiven User is on the homepage
    • check_circleWhen User navigate to logbook page
    • check_circleThen user should see the bars displayed only for days with logged activities
  • Medication Tracker Validation Jul 4, 2025 04:45:54 PM Fail
    check_circle cancel clear
    00 01 43.160
    cancel Scenario: Verify title in Medication form
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleWhen the user clicks Medication
    • cancelThen the user should see title "Diabetes Medication Tracker" after medication pop
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_i_t_l_e_ _i_n_ _M_e_d_i_c_a_t_i_o_n_ _f_o_r_m_
    00 01 11.050
    check_circle Scenario: Verify subtext in form
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see subtext "Keep track of your medications and never miss a dose"
    00 01 39.549
    cancel Scenario: Verify the heading in form
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see heading "Your Medications"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _h_e_a_d_i_n_g_ _i_n_ _f_o_r_m_
    00 01 18.381
    cancel Scenario: Verify the heading in flex
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see heading "Today's Medications" in flex
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _h_e_a_d_i_n_g_ _i_n_ _f_l_e_x_
    00 01 16.476
    cancel Scenario: Verify the presence of date picker
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see date picker in tracker
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _d_a_t_e_ _p_i_c_k_e_r_
    00 01 10.094
    check_circle Scenario: Verify the default value in datepicker
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see today's date as default value in datepicker
    00 02 50.444
    cancel Scenario: Verify message if no medication is added
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see message "No medications added yet\nClick the 'Add Medication' button to get started"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _m_e_s_s_a_g_e_ _i_f_ _n_o_ _m_e_d_i_c_a_t_i_o_n_ _i_s_ _a_d_d_e_d_
    • cancelhooks.Hooks.quitBrowser()
    00 01 04.971
    check_circle Scenario: Verify the presence of Add Medication button
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see Add medication button
    00 02 18.014
    cancel Scenario: Verify the presence of Close button
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see Close button in the form
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _C_l_o_s_e_ _b_u_t_t_o_n_
    00 03 26.760
    cancel Scenario: Verify presence of iframe
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleWhen the user clicks Add Medication
    • cancelThen the user should see iframe
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 47.394
    cancel Scenario: Verify the presence of Cancel button
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see Cancel button
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    • cancelhooks.Hooks.quitBrowser()
    00 02 55.056
    cancel Scenario: Verify heading in iframe
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see headingafter clicking add medication "Add new medication"
      Step undefined
    00 02 53.745
    check_circle Scenario: Verify the fields in iframe
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see fields "Medication, Dosage, Frequency, Date, Take with food, Notes (optional)"
    00 04 34.016
    cancel Scenario: Verify dropdown in medication field
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see dropdown for Medication
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    • cancelhooks.Hooks.quitBrowser()
    00 04 55.560
    cancel Scenario: Verify options in medication dropdown
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see following options in medication dropdown:
      Select a medication
      Metformin (Oral)
      Glipizide (Oral)
      Januvia (Oral)
      Jardiance (Oral)
      Trulicity (Injectable)
      Insulin Glargine (Injectable)
      Insulin Lispro (Injectable)
      Insulin NPH (Injectable)
      Other (Custom Medication)
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 48.654
    check_circle Scenario: Verify dosage input field
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see input field for Dosage
    00 06 51.219
    check_circle Scenario: Verify dosage placeholder
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see placeholder text "e.g., 500mg or 10 units"
    00 03 51.998
    cancel Scenario: Verify dropdown for frequency
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see dropdown for Frequency
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _d_r_o_p_d_o_w_n_ _f_o_r_ _f_r_e_q_u_e_n_c_y_
    00 07 28.363
    cancel Scenario: Verify options for frequency
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 32.661
    cancel Scenario: Verify checkbox for Take with food
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see checkbox for Take with food
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 29.083
    cancel Scenario: Verify text block for Notes
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see text block for Notes
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 36.309
    check_circle Scenario: Verify Add Medication button
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see Add medication button
    00 06 38.767
    cancel Scenario: Add medication with valid data
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 00.379
    cancel Scenario: Verify scheduled time for twice daily
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 03.983
    cancel Scenario: Verify scheduled time for once daily
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 44.764
    cancel Scenario: Verify scheduled time for three times daily
    @PremiumUser_LogbookPhysicalActivity
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 25.791
    cancel Scenario: Add medication without dosage
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 10.030
    cancel Scenario: Add medication with invalid dosage
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user enters invalid dosage and clicks Add Medication
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 27.042
    cancel Scenario: Verify today's date is highlighted
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 49.049
    cancel Scenario: Verify presence of previous and next buttons in calendar
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see Previous and Next buttons in the date picker
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_r_e_s_e_n_c_e_ _o_f_ _p_r_e_v_i_o_u_s_ _a_n_d_ _n_e_x_t_ _b_u_t_t_o_n_s_ _i_n_ _c_a_l_e_n_d_a_r_
    00 07 29.469
    cancel Scenario: Remove selected medication from dropdown
    @PremiumUser_LogbookPhysicalActivity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 29.276
    cancel Scenario: Verify datepicker popup
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 02.615
    cancel Scenario: Verify user can select previous date
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 14.073
    cancel Scenario: Verify note field character limit
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 03.359
    cancel Scenario: Remove added medication
    @PremiumUser_LogbookMedicalDosage
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 21.006
    cancel Scenario: Confirm medication removal
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user accepts the alert
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 06.644
    cancel Scenario: Cancel medication removal
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user declines the alert
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _C_a_n_c_e_l_ _m_e_d_i_c_a_t_i_o_n_ _r_e_m_o_v_a_l_
    00 02 58.238
    cancel Scenario: Mark medication as taken
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user clicks Mark as Taken button
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _M_a_r_k_ _m_e_d_i_c_a_t_i_o_n_ _a_s_ _t_a_k_e_n_
  • Medication Tracker Validation Jul 4, 2025 04:46:27 PM Fail
    check_circle cancel clear
    00 03 09.587
    cancel Scenario: Verify title in Medication form
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleWhen the user clicks Medication
    • cancelThen the user should see title "Diabetes Medication Tracker" after medication pop
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 20.522
    cancel Scenario: Verify subtext in form
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see subtext "Keep track of your medications and never miss a dose"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _s_u_b_t_e_x_t_ _i_n_ _f_o_r_m_
    00 02 52.455
    cancel Scenario: Verify the heading in form
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see heading "Your Medications"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 30.507
    cancel Scenario: Verify the heading in flex
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see heading "Today's Medications" in flex
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 28.564
    cancel Scenario: Verify the presence of date picker
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see date picker in tracker
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _d_a_t_e_ _p_i_c_k_e_r_
    00 03 31.355
    cancel Scenario: Verify the default value in datepicker
    @PremiumUser_Exercise
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see today's date as default value in datepicker
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _d_e_f_a_u_l_t_ _v_a_l_u_e_ _i_n_ _d_a_t_e_p_i_c_k_e_r_
    00 03 27.866
    cancel Scenario: Verify message if no medication is added
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see message "No medications added yet\nClick the 'Add Medication' button to get started"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _m_e_s_s_a_g_e_ _i_f_ _n_o_ _m_e_d_i_c_a_t_i_o_n_ _i_s_ _a_d_d_e_d_
    00 03 08.395
    check_circle Scenario: Verify the presence of Add Medication button
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see Add medication button
    00 03 22.069
    cancel Scenario: Verify the presence of Close button
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see Close button in the form
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _C_l_o_s_e_ _b_u_t_t_o_n_
    00 05 09.769
    cancel Scenario: Verify presence of iframe
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleWhen the user clicks Add Medication
    • cancelThen the user should see iframe
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 35.351
    cancel Scenario: Verify the presence of Cancel button
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see Cancel button
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 43.343
    cancel Scenario: Verify the fields in iframe
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see fields "Medication, Dosage, Frequency, Date, Take with food, Notes (optional)"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 41.605
    cancel Scenario: Verify heading in iframe
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see headingafter clicking add medication "Add new medication"
      Step undefined
    00 04 01.788
    cancel Scenario: Verify dropdown in medication field
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see dropdown for Medication
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _d_r_o_p_d_o_w_n_ _i_n_ _m_e_d_i_c_a_t_i_o_n_ _f_i_e_l_d_
    • cancelhooks.Hooks.quitBrowser()
    00 04 40.952
    cancel Scenario: Verify options in medication dropdown
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see following options in medication dropdown:
      Select a medication
      Metformin (Oral)
      Glipizide (Oral)
      Januvia (Oral)
      Jardiance (Oral)
      Trulicity (Injectable)
      Insulin Glargine (Injectable)
      Insulin Lispro (Injectable)
      Insulin NPH (Injectable)
      Other (Custom Medication)
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 38.386
    cancel Scenario: Verify dosage input field
    @PremiumUser_Exercise
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see input field for Dosage
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 38.782
    check_circle Scenario: Verify dosage placeholder
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see placeholder text "e.g., 500mg or 10 units"
    00 04 44.156
    cancel Scenario: Verify dropdown for frequency
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see dropdown for Frequency
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 05 42.147
    cancel Scenario: Verify options for frequency
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see following options in frequency dropdown:
      Once daily
      Twice daily
      Three times daily
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 40.180
    cancel Scenario: Verify checkbox for Take with food
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 37.327
    cancel Scenario: Verify text block for Notes
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 33.331
    cancel Scenario: Verify Add Medication button
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 11.639
    cancel Scenario: Add medication with valid data
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 43.351
    cancel Scenario: Verify scheduled time for twice daily
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleWhen the user selects Twice daily in frequency
    • cancelThen the user should see Scheduled at 8:00 and 20:00
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _s_c_h_e_d_u_l_e_d_ _t_i_m_e_ _f_o_r_ _t_w_i_c_e_ _d_a_i_l_y_
    00 02 56.329
    cancel Scenario: Add medication without dosage
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user leaves dosage field blank and clicks Add Medication
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _A_d_d_ _m_e_d_i_c_a_t_i_o_n_ _w_i_t_h_o_u_t_ _d_o_s_a_g_e_
    00 00 28.504
    cancel Scenario: Verify scheduled time for three times daily
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 00 26.885
    cancel Scenario: Verify scheduled time for once daily
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 10.776
    cancel Scenario: Add medication with invalid dosage
    @PremiumUser_LogbookPhysicalActivity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 16.718
    cancel Scenario: Remove selected medication from dropdown
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 12.097
    cancel Scenario: Verify datepicker popup
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 11.092
    cancel Scenario: Verify today's date is highlighted
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 28.173
    cancel Scenario: Verify presence of previous and next buttons in calendar
    @PremiumUser_Exercise
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 28.050
    cancel Scenario: Verify user can select previous date
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 10.190
    cancel Scenario: Verify note field character limit
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 47.621
    cancel Scenario: Remove added medication
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user clicks Remove button for an added medication
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _R_e_m_o_v_e_ _a_d_d_e_d_ _m_e_d_i_c_a_t_i_o_n_
    00 03 09.360
    cancel Scenario: Confirm medication removal
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user accepts the alert
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _C_o_n_f_i_r_m_ _m_e_d_i_c_a_t_i_o_n_ _r_e_m_o_v_a_l_
    00 03 14.560
    cancel Scenario: Cancel medication removal
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user declines the alert
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 32.917
    cancel Scenario: Mark medication as taken
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user clicks Mark as Taken button
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Medication Tracker Validation Jul 4, 2025 04:46:47 PM Fail
    check_circle cancel clear
    00 03 34.335
    cancel Scenario: Verify title in Medication form
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleWhen the user clicks Medication
    • cancelThen the user should see title "Diabetes Medication Tracker" after medication pop
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 42.859
    cancel Scenario: Verify subtext in form
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see subtext "Keep track of your medications and never miss a dose"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 29.738
    cancel Scenario: Verify the heading in form
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see heading "Your Medications"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 32.725
    cancel Scenario: Verify the heading in flex
    @PremiumUser_Exercise
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see heading "Today's Medications" in flex
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 05 21.552
    cancel Scenario: Verify the presence of date picker
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see date picker in tracker
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 03.196
    check_circle Scenario: Verify the default value in datepicker
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see today's date as default value in datepicker
    00 05 25.044
    cancel Scenario: Verify message if no medication is added
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see message "No medications added yet\nClick the 'Add Medication' button to get started"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _m_e_s_s_a_g_e_ _i_f_ _n_o_ _m_e_d_i_c_a_t_i_o_n_ _i_s_ _a_d_d_e_d_
    00 04 55.882
    cancel Scenario: Verify the presence of Add Medication button
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see Add medication button
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 09 01.862
    cancel Scenario: Verify the presence of Close button
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see Close button in the form
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _C_l_o_s_e_ _b_u_t_t_o_n_
    00 07 20.964
    cancel Scenario: Verify presence of iframe
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleWhen the user clicks Add Medication
    • cancelThen the user should see iframe
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 42.387
    check_circle Scenario: Verify the presence of Cancel button
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see Cancel button
    00 02 40.838
    cancel Scenario: Verify heading in iframe
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see headingafter clicking add medication "Add new medication"
      Step undefined
    00 04 17.637
    cancel Scenario: Verify the fields in iframe
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see fields "Medication, Dosage, Frequency, Date, Take with food, Notes (optional)"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 57.913
    cancel Scenario: Verify dropdown in medication field
    @PremiumUser_Exercise
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see dropdown for Medication
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    • cancelhooks.Hooks.quitBrowser()
    00 07 38.910
    cancel Scenario: Verify options in medication dropdown
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see following options in medication dropdown:
      Select a medication
      Metformin (Oral)
      Glipizide (Oral)
      Januvia (Oral)
      Jardiance (Oral)
      Trulicity (Injectable)
      Insulin Glargine (Injectable)
      Insulin Lispro (Injectable)
      Insulin NPH (Injectable)
      Other (Custom Medication)
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 41.798
    cancel Scenario: Verify dosage placeholder
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 40.409
    cancel Scenario: Verify dosage input field
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 33.654
    cancel Scenario: Verify dropdown for frequency
    @PremiumUser_LogbookMedicalDosage
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 13.543
    cancel Scenario: Verify options for frequency
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 11.887
    cancel Scenario: Verify checkbox for Take with food
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 15.987
    check_circle Scenario: Verify Add Medication button
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleThen the user should see Add medication button
    00 02 41.360
    cancel Scenario: Verify text block for Notes
    • cancelGiven the user is on the home page after logging into the app
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_e_x_t_ _b_l_o_c_k_ _f_o_r_ _N_o_t_e_s_
    00 02 47.291
    cancel Scenario: Verify scheduled time for twice daily
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleWhen the user selects Twice daily in frequency
    • cancelThen the user should see Scheduled at 8:00 and 20:00
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 59.890
    cancel Scenario: Verify scheduled time for once daily
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleWhen the user selects Once daily in frequency
    • cancelThen the user should see Scheduled at 8:00
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _s_c_h_e_d_u_l_e_d_ _t_i_m_e_ _f_o_r_ _o_n_c_e_ _d_a_i_l_y_
    00 03 54.442
    cancel Scenario: Add medication with valid data
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user fills out the medication form with valid data
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _A_d_d_ _m_e_d_i_c_a_t_i_o_n_ _w_i_t_h_ _v_a_l_i_d_ _d_a_t_a_
    00 07 26.185
    cancel Scenario: Verify scheduled time for three times daily
    @PremiumUser_Exercise
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 10.564
    cancel Scenario: Add medication without dosage
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 20.951
    cancel Scenario: Add medication with invalid dosage
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 22.843
    cancel Scenario: Remove selected medication from dropdown
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is on the home page after logging into the app
    • check_circleWhen the user selects a medication
    • cancelThen the user should see remove icon "X"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 19.825
    cancel Scenario: Verify datepicker popup
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user clicks the date field
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 15.608
    cancel Scenario: Verify today's date is highlighted
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see today's date highlighted in the calendar
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_o_d_a_y_'_s_ _d_a_t_e_ _i_s_ _h_i_g_h_l_i_g_h_t_e_d_
    00 03 09.423
    cancel Scenario: Verify presence of previous and next buttons in calendar
    • check_circleGiven the user is on the home page after logging into the app
    • cancelThen the user should see Previous and Next buttons in the date picker
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_r_e_s_e_n_c_e_ _o_f_ _p_r_e_v_i_o_u_s_ _a_n_d_ _n_e_x_t_ _b_u_t_t_o_n_s_ _i_n_ _c_a_l_e_n_d_a_r_
    00 04 02.103
    cancel Scenario: Verify user can select previous date
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user selects previous date
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 35.100
    cancel Scenario: Verify note field character limit
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 33.642
    cancel Scenario: Remove added medication
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 31.551
    cancel Scenario: Confirm medication removal
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user accepts the alert
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _C_o_n_f_i_r_m_ _m_e_d_i_c_a_t_i_o_n_ _r_e_m_o_v_a_l_
    00 02 25.993
    cancel Scenario: Cancel medication removal
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user declines the alert
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 31.486
    cancel Scenario: Mark medication as taken
    • check_circleGiven the user is on the home page after logging into the app
    • cancelWhen the user clicks Mark as Taken button
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _M_a_r_k_ _m_e_d_i_c_a_t_i_o_n_ _a_s_ _t_a_k_e_n_
  • Physical Activity Validation and Food Intake Jul 4, 2025 04:57:14 PM Fail
    check_circle cancel clear
    00 03 36.153
    cancel Scenario: Verify title in Food Intake form
    @physicalActity @FoodIntake
    • check_circleGiven User is in home page after logged into app
    • check_circleWhen User clicks Food Intake
    • cancelThen User should see title "Food Intake Tracker" on food popup
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 15.857
    check_circle Scenario: Verify subtext in form
    @physicalActity @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see subtext "Track what you eat to manage your diabetes better" in the food popup
    00 02 31.717
    cancel Scenario: Verify presence of 4 tabs
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see "Breakfast, Lunch, Dinner, Snack" tabs
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_r_e_s_e_n_c_e_ _o_f_ _4_ _t_a_b_s_
    00 02 27.048
    cancel Scenario: Verify fields in Food Intake form
    @physicalActity @PremiumUser_LogbookLogReview
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see field for Food Name, Serving Size, Calories, Date, Notes
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _f_i_e_l_d_s_ _i_n_ _F_o_o_d_ _I_n_t_a_k_e_ _f_o_r_m_
    00 02 57.731
    cancel Scenario: Verify default meal tab
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see "Breakfast" tab selected by default
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 35.585
    check_circle Scenario: Verify input field for food name
    @physicalActity @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see input field for food name
    00 01 38.996
    check_circle Scenario: Verify placeholder in food name field
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see text "e.g., Grilled Chicken Salad" as placeholder
    00 07 07.280
    cancel Scenario: Verify dropdown for Serving Size
    @physicalActity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 11.595
    cancel Scenario: Verify options in Serving Size
    @physicalActity @PremiumUser_LogbookPhysicalActivity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 06.875
    cancel Scenario: Verify default value in Serving Size
    @physicalActity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 10.362
    cancel Scenario: Verify calculator icon in calorie field
    @physicalActity @PremiumUser_LogbookMedicalDosage
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 10.253
    cancel Scenario: Verify input field for calorie
    @physicalActity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 29.930
    cancel Scenario: Verify placeholder in calorie field
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see text "eg.250" as placeholder
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 42.597
    cancel Scenario: Verify helper text under calorie field
    @physicalActity @PremiumUser_LogbookLogReview
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see "Enter calories or click the calculator icon for automatic calculation." after popoup
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 38.956
    cancel Scenario: Verify date picker after popup
    @physicalActity @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see date picker
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 31.780
    cancel Scenario: Verify default value in Date field
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see toadys date
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 05.751
    cancel Scenario: Verify input for notes
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see input block for notes
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _i_n_p_u_t_ _f_o_r_ _n_o_t_e_s_
    00 02 35.941
    check_circle Scenario: Verify placeholder in notes
    @physicalActity @PremiumUser_LogbookLogReview
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see "Add any additional information..."after the foodintake popup
    00 03 12.331
    cancel Scenario: Verify save food entry button
    @physicalActity @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see save food entry button
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _s_a_v_e_ _f_o_o_d_ _e_n_t_r_y_ _b_u_t_t_o_n_
  • Physical Activity Validation and Food Intake Jul 4, 2025 05:00:14 PM Fail
    check_circle cancel clear
    00 03 06.815
    cancel Scenario: Verify title in Food Intake form
    @physicalActity @FoodIntake
    • check_circleGiven User is in home page after logged into app
    • check_circleWhen User clicks Food Intake
    • cancelThen User should see title "Food Intake Tracker" on food popup
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_i_t_l_e_ _i_n_ _F_o_o_d_ _I_n_t_a_k_e_ _f_o_r_m_
    00 01 55.738
    cancel Scenario: Verify presence of 4 tabs
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see "Breakfast, Lunch, Dinner, Snack" tabs
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_r_e_s_e_n_c_e_ _o_f_ _4_ _t_a_b_s_
    00 01 41.228
    check_circle Scenario: Verify subtext in form
    @physicalActity @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see subtext "Track what you eat to manage your diabetes better" in the food popup
    00 02 31.506
    cancel Scenario: Verify fields in Food Intake form
    @physicalActity @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see field for Food Name, Serving Size, Calories, Date, Notes
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _f_i_e_l_d_s_ _i_n_ _F_o_o_d_ _I_n_t_a_k_e_ _f_o_r_m_
    00 01 32.691
    check_circle Scenario: Verify default meal tab
    @physicalActity @PremiumUser_LogbookLogReview
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see "Breakfast" tab selected by default
    00 07 14.944
    cancel Scenario: Verify input field for food name
    @physicalActity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 05.056
    cancel Scenario: Verify placeholder in food name field
    @physicalActity @PremiumUser_Exercise
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 15.505
    cancel Scenario: Verify dropdown for Serving Size
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see dropdown for serving size
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 21.788
    check_circle Scenario: Verify default value in Serving Size
    @physicalActity @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see "Medium (1 cup)" as default
    00 04 05.456
    cancel Scenario: Verify options in Serving Size
    @physicalActity @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see "Small (1/2 cup), Medium (1 cup), Large (2 cups), Custom" in foodIntake popup
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 01.328
    cancel Scenario: Verify calculator icon in calorie field
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see calculator icon in calorie
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 28.342
    cancel Scenario: Verify input field for calorie
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see input field for calorie
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 34.975
    cancel Scenario: Verify placeholder in calorie field
    @physicalActity @PremiumUser_LogbookLogReview
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see text "eg.250" as placeholder
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 07.614
    check_circle Scenario: Verify helper text under calorie field
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see "Enter calories or click the calculator icon for automatic calculation." after popoup
    00 04 04.413
    cancel Scenario: Verify date picker after popup
    @physicalActity @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see date picker
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 49.033
    cancel Scenario: Verify default value in Date field
    @physicalActity @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see toadys date
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 10.894
    check_circle Scenario: Verify input for notes
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see input block for notes
    00 02 48.198
    check_circle Scenario: Verify placeholder in notes
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see "Add any additional information..."after the foodintake popup
    00 02 32.035
    cancel Scenario: Verify save food entry button
    @physicalActity
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Physical Activity Validation and Food Intake Jul 4, 2025 05:00:14 PM Fail
    check_circle cancel clear
    00 02 42.086
    cancel Scenario: Verify title in Food Intake form
    @physicalActity @FoodIntake
    • check_circleGiven User is in home page after logged into app
    • check_circleWhen User clicks Food Intake
    • cancelThen User should see title "Food Intake Tracker" on food popup
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_i_t_l_e_ _i_n_ _F_o_o_d_ _I_n_t_a_k_e_ _f_o_r_m_
    00 01 31.826
    check_circle Scenario: Verify subtext in form
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see subtext "Track what you eat to manage your diabetes better" in the food popup
    00 07 24.486
    cancel Scenario: Verify presence of 4 tabs
    @physicalActity @PremiumUser_LogbookPhysicalActivity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 10.016
    cancel Scenario: Verify input field for food name
    @physicalActity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 09.447
    cancel Scenario: Verify default meal tab
    @physicalActity @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 13.360
    cancel Scenario: Verify fields in Food Intake form
    @physicalActity @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see field for Food Name, Serving Size, Calories, Date, Notes
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _f_i_e_l_d_s_ _i_n_ _F_o_o_d_ _I_n_t_a_k_e_ _f_o_r_m_
    00 07 07.143
    cancel Scenario: Verify placeholder in food name field
    @physicalActity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 16.522
    check_circle Scenario: Verify default value in Serving Size
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see "Medium (1 cup)" as default
    00 03 14.720
    cancel Scenario: Verify dropdown for Serving Size
    @physicalActity @PremiumUser_Exercise
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see dropdown for serving size
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 10 52.971
    cancel Scenario: Verify options in Serving Size
    @physicalActity @PremiumUser_LogbookLogReview
    • cancelGiven User is in home page after logged into app
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 02.633
    cancel Scenario: Verify calculator icon in calorie field
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see calculator icon in calorie
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 45.130
    cancel Scenario: Verify input field for calorie
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see input field for calorie
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 56.245
    cancel Scenario: Verify placeholder in calorie field
    @physicalActity @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see text "eg.250" as placeholder
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 57.687
    cancel Scenario: Verify helper text under calorie field
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see "Enter calories or click the calculator icon for automatic calculation." after popoup
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _h_e_l_p_e_r_ _t_e_x_t_ _u_n_d_e_r_ _c_a_l_o_r_i_e_ _f_i_e_l_d_
    00 03 47.748
    cancel Scenario: Verify default value in Date field
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see toadys date
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 57.950
    cancel Scenario: Verify date picker after popup
    @physicalActity @PremiumUser_Exercise
    • check_circleGiven User is in home page after logged into app
    • cancelThen User should see date picker
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 38.534
    cancel Scenario: Verify input for notes
    @physicalActity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 28.470
    cancel Scenario: Verify placeholder in notes
    @physicalActity @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 31.707
    check_circle Scenario: Verify save food entry button
    @physicalActity
    • check_circleGiven User is in home page after logged into app
    • check_circleThen User should see save food entry button
  • Functional and Non-Functional Test Validation for Premium Account User Jul 4, 2025 05:06:39 PM Fail
    check_circle cancel clear
    00 03 49.512
    cancel Scenario: Verify the presence of icon for Pre-meal
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 25.698
    cancel Scenario: Verify the presence of "Pre-meal" title in each meal section
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 29.443
    cancel Scenario: Verify pre-meal title is shown before main meal
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_r_e_-_m_e_a_l_ _t_i_t_l_e_ _i_s_ _s_h_o_w_n_ _b_e_f_o_r_e_ _m_a_i_n_ _m_e_a_l_
    00 01 50.578
    check_circle Scenario: Verify "None" is displayed for Pre-Meal Snack by default
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks snack section
    • check_circleThen the user should see Pre-Meal entry displays as "None" by default
    00 01 57.842
    cancel Scenario: Verify calorie in pre-meal snack
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _c_a_l_o_r_i_e_ _i_n_ _p_r_e_-_m_e_a_l_ _s_n_a_c_k_
    00 07 01.740
    cancel Scenario: Verify the presence of meal title for main meal in snack
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 27.122
    cancel Scenario: Verify meal section contains dish description in snack
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 30.757
    cancel Scenario: Verify the presence of Sub title "Main-Meal"
    @physicalActity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _S_u_b_ _t_i_t_l_e_ _"_M_a_i_n_-_M_e_a_l_"_
    00 07 12.392
    cancel Scenario: Verify the presence of icon for main-meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 15.353
    cancel Scenario: Verify the time format in each main-meal
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 13.234
    cancel Scenario: Validate the indicator for breakfast main-meal
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 06.724
    cancel Scenario: Validate the indicator for lunch main-meal
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_a_l_i_d_a_t_e_ _t_h_e_ _i_n_d_i_c_a_t_o_r_ _f_o_r_ _l_u_n_c_h_ _m_a_i_n_-_m_e_a_l_
    00 02 06.914
    cancel Scenario: Validate the indicator for dinner main-meal
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_a_l_i_d_a_t_e_ _t_h_e_ _i_n_d_i_c_a_t_o_r_ _f_o_r_ _d_i_n_n_e_r_ _m_a_i_n_-_m_e_a_l_
    00 02 54.889
    cancel Scenario: Validate the indicator for snack main-meal
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 50.387
    cancel Scenario: Verify the time in main-breakfast
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_m_e_ _i_n_ _m_a_i_n_-_b_r_e_a_k_f_a_s_t_
    00 10 52.559
    cancel Scenario: Verify the time in main-lunch
    @physicalActity
    • cancelGiven the user is in password auth page
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 34.850
    check_circle Scenario: Verify the time in main-dinner
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see 7:30 o'clock
    00 02 52.576
    cancel Scenario: Verify the time in main-snack
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 48.133
    cancel Scenario: Verify calories for main-meal is shown for each meal
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 45.095
    cancel Scenario: Validate the text "Calories" in main-meal
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 41.451
    cancel Scenario: Verify the presence of ✅ Completed button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _✅_ _C_o_m_p_l_e_t_e_d_ _b_u_t_t_o_n_
    00 03 29.280
    cancel Scenario: Verify the presence of ⚠️ Partially Completed button
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 28.235
    cancel Scenario: Verify the presence of ❌ Not Completed button
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 22.030
    check_circle Scenario: Verify color change of completed button
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user marks meal as completed
    • check_circleThen the button color should change to green
    00 01 22.348
    cancel Scenario: Verify color change of partially completed button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _c_o_l_o_r_ _c_h_a_n_g_e_ _o_f_ _p_a_r_t_i_a_l_l_y_ _c_o_m_p_l_e_t_e_d_ _b_u_t_t_o_n_
    00 01 52.120
    cancel Scenario: Verify color change of not completed button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _c_o_l_o_r_ _c_h_a_n_g_e_ _o_f_ _n_o_t_ _c_o_m_p_l_e_t_e_d_ _b_u_t_t_o_n_
    00 01 45.753
    cancel Scenario: Verify presence of nutrition insight summary card in each meal section
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _p_r_e_s_e_n_c_e_ _o_f_ _n_u_t_r_i_t_i_o_n_ _i_n_s_i_g_h_t_ _s_u_m_m_a_r_y_ _c_a_r_d_ _i_n_ _e_a_c_h_ _m_e_a_l_ _s_e_c_t_i_o_n_
    00 01 25.776
    cancel Scenario: Verify title in nutrition flex card
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user views a meal section
    • cancelThen the user should see title "Nutrition Insight"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_i_t_l_e_ _i_n_ _n_u_t_r_i_t_i_o_n_ _f_l_e_x_ _c_a_r_d_
    00 03 00.484
    cancel Scenario: Verify sub-title in nutrition flex card
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 57.546
    cancel Scenario: Verify total calorie count from pre-meal and meal
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 31.125
    cancel Scenario: Verify each meal calorie detail on the right side
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 19.974
    cancel Scenario: Verify navigation to View Full Meal Plan
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 54.415
    cancel Scenario: Verify title in View Meal Plan page
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 35.922
    cancel Scenario: Verify presence of Back to Plan button
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleGiven the user is on Full Meal Plan page
    • cancelWhen the user views navigation controls
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 53.371
    cancel Scenario: Verify meal section button in View Plan page
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Functional and Non-Functional Test Validation for Premium Account User Jul 4, 2025 05:07:19 PM Fail
    check_circle cancel clear
    00 04 05.887
    cancel Scenario: Verify the presence of "Pre-meal" title in each meal section
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • cancelThen the user should see "Pre-Meal" title under the four tabs
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 13.565
    cancel Scenario: Verify the presence of icon for Pre-meal
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 18.157
    cancel Scenario: Verify pre-meal title is shown before main meal
    @physicalActity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 19.783
    cancel Scenario: Verify "None" is displayed for Pre-Meal Snack by default
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 11 02.496
    cancel Scenario: Verify calorie in pre-meal snack
    • cancelGiven the user is in password auth page
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 03.722
    cancel Scenario: Verify the presence of meal title for main meal in snack
    @PremiumUser_LogbookPhysicalActivity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 23.634
    cancel Scenario: Verify meal section contains dish description in snack
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 15.426
    cancel Scenario: Verify the presence of icon for main-meal
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 14.464
    cancel Scenario: Verify the presence of Sub title "Main-Meal"
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 01.473
    cancel Scenario: Verify the time format in each main-meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_m_e_ _f_o_r_m_a_t_ _i_n_ _e_a_c_h_ _m_a_i_n_-_m_e_a_l_
    00 02 55.788
    cancel Scenario: Validate the indicator for breakfast main-meal
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 45.079
    cancel Scenario: Validate the indicator for lunch main-meal
    @physicalActity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_a_l_i_d_a_t_e_ _t_h_e_ _i_n_d_i_c_a_t_o_r_ _f_o_r_ _l_u_n_c_h_ _m_a_i_n_-_m_e_a_l_
    00 03 14.051
    cancel Scenario: Validate the indicator for dinner main-meal
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 44.214
    cancel Scenario: Validate the indicator for snack main-meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 33.186
    cancel Scenario: Verify the time in main-breakfast
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 59.068
    cancel Scenario: Verify the time in main-lunch
    @physicalActity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 16.351
    check_circle Scenario: Verify the time in main-dinner
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see 7:30 o'clock
    00 02 26.724
    cancel Scenario: Verify the time in main-snack
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_m_e_ _i_n_ _m_a_i_n_-_s_n_a_c_k_
    00 01 33.700
    check_circle Scenario: Verify calories for main-meal is shown for each meal
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see the main-meal calorie value
    00 01 21.561
    check_circle Scenario: Validate the text "Calories" in main-meal
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see text "Calories" after the calorie value in main meal
    00 01 21.536
    check_circle Scenario: Verify the presence of ✅ Completed button
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see "✅ Completed" button
    00 01 27.575
    check_circle Scenario: Verify the presence of ⚠️ Partially Completed button
    @physicalActity
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see "⚠️ Partially Completed" button
    00 02 21.436
    check_circle Scenario: Verify the presence of ❌ Not Completed button
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see "❌ Not Completed" button
    00 03 13.102
    cancel Scenario: Verify color change of completed button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 14.425
    cancel Scenario: Verify color change of partially completed button
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 05.239
    cancel Scenario: Verify color change of not completed button
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 14.156
    cancel Scenario: Verify presence of nutrition insight summary card in each meal section
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 12.909
    cancel Scenario: Verify title in nutrition flex card
    @PremiumUser_LogbookMedicalDosage
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 10.473
    check_circle Scenario: Verify sub-title in nutrition flex card
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see subtitle "Calories"
    00 04 08.492
    cancel Scenario: Verify total calorie count from pre-meal and meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 14.320
    check_circle Scenario: Verify each meal calorie detail on the right side
    @physicalActity
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see calorie detail on the right side of its section
    00 03 25.218
    cancel Scenario: Verify navigation to View Full Meal Plan
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 57.723
    cancel Scenario: Verify title in View Meal Plan page
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 30.734
    cancel Scenario: Verify presence of Back to Plan button
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleGiven the user is on Full Meal Plan page
    • cancelWhen the user views navigation controls
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 32.650
    cancel Scenario: Verify meal section button in View Plan page
    @physicalActity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Functional and Non-Functional Test Validation for Premium Account User Jul 4, 2025 05:09:05 PM Fail
    check_circle cancel clear
    00 07 07.520
    cancel Scenario: Verify the presence of "Pre-meal" title in each meal section
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 16.093
    cancel Scenario: Verify pre-meal title is shown before main meal
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 16.101
    cancel Scenario: Verify the presence of icon for Pre-meal
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 15.706
    cancel Scenario: Verify "None" is displayed for Pre-Meal Snack by default
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 07.298
    cancel Scenario: Verify calorie in pre-meal snack
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _c_a_l_o_r_i_e_ _i_n_ _p_r_e_-_m_e_a_l_ _s_n_a_c_k_
    00 02 15.125
    cancel Scenario: Verify the presence of meal title for main meal in snack
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _p_r_e_s_e_n_c_e_ _o_f_ _m_e_a_l_ _t_i_t_l_e_ _f_o_r_ _m_a_i_n_ _m_e_a_l_ _i_n_ _s_n_a_c_k_
    00 03 02.183
    cancel Scenario: Verify meal section contains dish description in snack
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 10 47.580
    cancel Scenario: Verify the presence of Sub title "Main-Meal"
    • cancelGiven the user is in password auth page
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 54.282
    cancel Scenario: Verify the presence of icon for main-meal
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 49.847
    cancel Scenario: Verify the time format in each main-meal
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 22.675
    cancel Scenario: Validate the indicator for breakfast main-meal
    @physicalActity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_a_l_i_d_a_t_e_ _t_h_e_ _i_n_d_i_c_a_t_o_r_ _f_o_r_ _b_r_e_a_k_f_a_s_t_ _m_a_i_n_-_m_e_a_l_
    00 02 28.357
    cancel Scenario: Validate the indicator for lunch main-meal
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 15.507
    check_circle Scenario: Validate the indicator for dinner main-meal
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see indicator "PM" for dinner main-meal
    00 01 26.832
    cancel Scenario: Validate the indicator for snack main-meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_a_l_i_d_a_t_e_ _t_h_e_ _i_n_d_i_c_a_t_o_r_ _f_o_r_ _s_n_a_c_k_ _m_a_i_n_-_m_e_a_l_
    00 01 24.206
    cancel Scenario: Verify the time in main-breakfast
    @physicalActity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_m_e_ _i_n_ _m_a_i_n_-_b_r_e_a_k_f_a_s_t_
    00 03 33.850
    cancel Scenario: Verify the time in main-lunch
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 28.736
    cancel Scenario: Verify the time in main-dinner
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 11.191
    cancel Scenario: Verify the time in main-snack
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _t_i_m_e_ _i_n_ _m_a_i_n_-_s_n_a_c_k_
    00 07 03.995
    cancel Scenario: Validate the text "Calories" in main-meal
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 04.712
    cancel Scenario: Verify the presence of ✅ Completed button
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 13.654
    cancel Scenario: Verify calories for main-meal is shown for each meal
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 05.908
    check_circle Scenario: Verify the presence of ⚠️ Partially Completed button
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see "⚠️ Partially Completed" button
    00 04 08.530
    check_circle Scenario: Verify the presence of ❌ Not Completed button
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see "❌ Not Completed" button
    00 03 21.723
    cancel Scenario: Verify color change of completed button
    @physicalActity
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 26.604
    cancel Scenario: Verify color change of partially completed button
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 46.429
    cancel Scenario: Verify color change of not completed button
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 46.497
    cancel Scenario: Verify presence of nutrition insight summary card in each meal section
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 01.803
    cancel Scenario: Verify title in nutrition flex card
    @PremiumUser_Exercise
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user views a meal section
    • cancelThen the user should see title "Nutrition Insight"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 29.796
    check_circle Scenario: Verify sub-title in nutrition flex card
    @physicalActity
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen the user should see subtitle "Calories"
    00 02 31.389
    check_circle Scenario: Verify total calorie count from pre-meal and meal
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks meal section
    • check_circleThen total calorie count should equal the sum of Pre-Meal and Meal calories
    00 02 49.155
    cancel Scenario: Verify each meal calorie detail on the right side
    @PremiumUser_LogbookLogReview
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _e_a_c_h_ _m_e_a_l_ _c_a_l_o_r_i_e_ _d_e_t_a_i_l_ _o_n_ _t_h_e_ _r_i_g_h_t_ _s_i_d_e_
    00 01 43.127
    check_circle Scenario: Verify navigation to View Full Meal Plan
    • check_circleGiven the user is in password auth page
    • check_circleWhen the user clicks sign in after entering password
    • check_circleWhen the user clicks View Meal Plan button
    • check_circleThen the user should be redirected to Full Meal Plan page
    00 02 11.905
    cancel Scenario: Verify title in View Meal Plan page
    • check_circleGiven the user is in password auth page
    • cancelWhen the user clicks sign in after entering password
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_i_t_l_e_ _i_n_ _V_i_e_w_ _M_e_a_l_ _P_l_a_n_ _p_a_g_e_
    00 02 13.657
    cancel Scenario: Verify presence of Back to Plan button
    @physicalActity
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 26.789
    cancel Scenario: Verify meal section button in View Plan page
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Homepage Challenge Button Functionality Jul 4, 2025 05:17:01 PM Fail
    check_circle cancel clear
    00 03 22.936
    cancel Scenario: Verify the navigation of the Challenge button
    • check_circleGiven User is logged into app
    • check_circleWhen User clicks Challenge button
    • cancelThen User should get pop window
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 48.750
    cancel Scenario: Verify the title of the popup
    • check_circleGiven User is logged into app
    • check_circleWhen User clicks Challenge button
    • cancelThen User should see title "Choose Your Challenge"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 03.659
    cancel Scenario: Verify the subtext in the popup
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User is logged into app
    • check_circleWhen User clicks Challenge button
    • cancelThen User should see sub text on challenge popup "Select a program that best fits your health goals"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 03.544
    cancel Scenario: Verify the presence of two option buttons
    • check_circleGiven User is logged into app
    • check_circleWhen User clicks Challenge button
    • cancelThen User should see two options for challenge option
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 48.975
    cancel Scenario: Verify the first option text
    • check_circleGiven User is logged into app
    • check_circleWhen User clicks Challenge button
    • cancelThen User should see "10-Day Challenge Postprandial Blood Glucose Reduction" as first option
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 47.030
    cancel Scenario: Verify the second option text
    • check_circleGiven User is logged into app
    • check_circleWhen User clicks Challenge button
    • cancelThen User should see "4-Week Program Blood Sugar Reduction Plan" as first option
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _s_e_c_o_n_d_ _o_p_t_i_o_n_ _t_e_x_t_
  • Homepage Challenge Button Functionality Jul 4, 2025 05:20:16 PM Fail
    check_circle cancel clear
    00 04 01.485
    cancel Scenario: Verify the navigation of the Challenge button
    • check_circleGiven User is logged into app
    • check_circleWhen User clicks Challenge button
    • cancelThen User should get pop window
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 26.838
    cancel Scenario: Verify the title of the popup
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 18.596
    cancel Scenario: Verify the subtext in the popup
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is logged into app
    • check_circleWhen User clicks Challenge button
    • cancelThen User should see sub text on challenge popup "Select a program that best fits your health goals"
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _s_u_b_t_e_x_t_ _i_n_ _t_h_e_ _p_o_p_u_p_
    00 01 33.580
    cancel Scenario: Verify the presence of two option buttons
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 26.065
    cancel Scenario: Verify the first option text
    @physicalActity
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 01.838
    cancel Scenario: Verify the second option text
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • verification on log status Jul 4, 2025 05:20:24 PM Pass
    check_circle cancel clear
    00 02 49.376
    check_circle Scenario: Verify user able to change the log
    • check_circleGiven User is in dashboard page
    • check_circleWhen User clicks home tab after logging emotional state in dashboard
    • check_circleThen User should see emoji and mood text is changed
  • Validation for View Full Meal Plan Jul 4, 2025 05:20:55 PM Fail
    check_circle cancel clear
    00 04 09.755
    cancel Scenario: Verify pre-meal includes description under the item name
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen Item description should be displayed below the item name
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 35.469
    cancel Scenario: Verify each meal section has Pre meal title
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleGiven User is in View Meal plan
    • check_circleWhen User clicks Meal sections
    • cancelThen Each meal section should display a pre-meal item with the format "Pre-meal: "
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 59.323
    cancel Scenario: Verify Pre meal calorie in view full plan
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen Calories value should be displayed
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 45.129
    check_circle Scenario: Verify pre meal preparation in view full plan
    @physicalActity
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen Preparation instructions displayed if available, if not then "N/A"
    00 01 56.827
    check_circle Scenario: Verify Nutrients (Pre-meal portion)
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen User should see "Nutrients (Pre-meal portion)" heading in full plan
    00 03 34.284
    cancel Scenario: Verify nutrients list (Pre-meal portion)
    @PremiumUser_LogbookMedicalDosage
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen User should see list "carb, protein, fat, fibre"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 40.302
    cancel Scenario: Verify meal includes description under the item name
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 14.045
    cancel Scenario: Verify meal preparation
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 16.323
    cancel Scenario: Verify Nutrients information
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 28.467
    check_circle Scenario: Verify nutrients list (meal portion)
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen User should see "carb, protein, fat, fibre"
    00 01 41.032
    check_circle Scenario: Verify Diabetes Management Tips heading
    @physicalActity
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen User should see heading "Diabetes Management Tips"
    00 03 37.809
    cancel Scenario: Validate back to plan button
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleGiven User is in view full plan page
    • check_circleWhen User clicks back to plan button
    • cancelThen User should redirected to Home page
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Homepage Challenge Button Functionality Jul 4, 2025 05:23:29 PM Fail
    check_circle cancel clear
    00 02 14.604
    cancel Scenario: Verify the navigation of the Challenge button
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 25.757
    cancel Scenario: Verify the title of the popup
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 27.889
    cancel Scenario: Verify the subtext in the popup
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 11.664
    cancel Scenario: Verify the presence of two option buttons
    @PremiumUser_Exercise
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 11.067
    cancel Scenario: Verify the first option text
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 42.538
    cancel Scenario: Verify the second option text
    • check_circleGiven User is logged into app
    • check_circleWhen User clicks Challenge button
    • cancelThen User should see "4-Week Program Blood Sugar Reduction Plan" as first option
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _s_e_c_o_n_d_ _o_p_t_i_o_n_ _t_e_x_t_
  • verification on log status Jul 4, 2025 05:23:36 PM Fail
    check_circle cancel clear
    00 02 09.822
    cancel Scenario: Verify user able to change the log
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Validation for View Full Meal Plan Jul 4, 2025 05:23:38 PM Fail
    check_circle cancel clear
    00 02 17.146
    cancel Scenario: Verify pre-meal includes description under the item name
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 06.596
    cancel Scenario: Verify each meal section has Pre meal title
    • cancelhooks.Hooks.launchbrowser()
    • cancelstepdefinition.PremiumUser_HomePageSD.init()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 10.325
    cancel Scenario: Verify Pre meal calorie in view full plan
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen Calories value should be displayed
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 27.495
    cancel Scenario: Verify pre meal preparation in view full plan
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen Preparation instructions displayed if available, if not then "N/A"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 22.494
    check_circle Scenario: Verify Nutrients (Pre-meal portion)
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen User should see "Nutrients (Pre-meal portion)" heading in full plan
    00 03 30.550
    cancel Scenario: Verify nutrients list (Pre-meal portion)
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen User should see list "carb, protein, fat, fibre"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 51.506
    cancel Scenario: Verify meal includes description under the item name
    @PremiumUser_LogbookLogReview
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen Item description should be displayed below the item name
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 59.722
    check_circle Scenario: Verify meal preparation
    @physicalActity
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen Preparation instructions displayed if available, if not then "N/A"
    00 02 57.930
    check_circle Scenario: Verify Nutrients information
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen User should see "Nutrients information" heading in full plan
    00 02 57.559
    check_circle Scenario: Verify nutrients list (meal portion)
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen User should see "carb, protein, fat, fibre"
    00 02 48.383
    check_circle Scenario: Verify Diabetes Management Tips heading
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen User should see heading "Diabetes Management Tips"
    00 07 33.474
    cancel Scenario: Validate back to plan button
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • verification on log status Jul 4, 2025 05:24:48 PM Pass
    check_circle cancel clear
    00 01 27.118
    check_circle Scenario: Verify user able to change the log
    • check_circleGiven User is in dashboard page
    • check_circleWhen User clicks home tab after logging emotional state in dashboard
    • check_circleThen User should see emoji and mood text is changed
  • Verification on button navigation in home page Jul 4, 2025 05:24:57 PM Fail
    check_circle cancel clear
    00 01 18.966
    check_circle Scenario: Verify user able to download weekly plan
    • check_circleGiven User logged onto the application
    • check_circleGiven User is in home page
    • check_circleWhen User clicks Weekly plan
    • check_circleThen User should get pdf download of weekly plan
    00 03 08.557
    cancel Scenario: Verify the navigation of Blood Glucose button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on Blood glucose button
    • cancelThen User should redirect to Blood Glucose popup window
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 01.511
    cancel Scenario: Verify the navigation of Physical Activity button
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on physical activity button
    • cancelThen User should redirect to physical activity popup window
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 54.415
    cancel Scenario: Verify the navigation of Food Intake button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on food intake button
    • cancelThen User should redirect to food intake popup window
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _F_o_o_d_ _I_n_t_a_k_e_ _b_u_t_t_o_n_
    00 03 36.522
    cancel Scenario: Verify the navigation of Medication button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on medication button
    • cancelThen User should redirect to medication popup window
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _M_e_d_i_c_a_t_i_o_n_ _b_u_t_t_o_n_
    00 04 29.393
    cancel Scenario: Verify the navigation of log button
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks log button
    • cancelThen User should redirected to dashboard page
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Validation for View Full Meal Plan Jul 4, 2025 05:25:13 PM Fail
    check_circle cancel clear
    00 03 30.022
    cancel Scenario: Verify each meal section has Pre meal title
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleGiven User is in View Meal plan
    • check_circleWhen User clicks Meal sections
    • cancelThen Each meal section should display a pre-meal item with the format "Pre-meal: "
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 00.162
    cancel Scenario: Verify pre-meal includes description under the item name
    @physicalActity
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen Item description should be displayed below the item name
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 05 09.778
    cancel Scenario: Verify Pre meal calorie in view full plan
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen Calories value should be displayed
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 48.816
    check_circle Scenario: Verify pre meal preparation in view full plan
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen Preparation instructions displayed if available, if not then "N/A"
    00 07 16.799
    cancel Scenario: Verify Nutrients (Pre-meal portion)
    @PremiumUser_Exercise
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 55.890
    cancel Scenario: Verify nutrients list (Pre-meal portion)
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen User should see list "carb, protein, fat, fibre"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 06.180
    cancel Scenario: Verify meal includes description under the item name
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen Item description should be displayed below the item name
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 43.239
    cancel Scenario: Verify meal preparation
    • check_circleGiven User clicks view meal plan after reaching home page
    • cancelThen Preparation instructions displayed if available, if not then "N/A"
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 05.539
    check_circle Scenario: Verify Nutrients information
    @physicalActity
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen User should see "Nutrients information" heading in full plan
    00 02 12.452
    check_circle Scenario: Verify nutrients list (meal portion)
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen User should see "carb, protein, fat, fibre"
    00 02 11.489
    check_circle Scenario: Verify Diabetes Management Tips heading
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleThen User should see heading "Diabetes Management Tips"
    00 03 35.120
    cancel Scenario: Validate back to plan button
    • check_circleGiven User clicks view meal plan after reaching home page
    • check_circleGiven User is in view full plan page
    • check_circleWhen User clicks back to plan button
    • cancelThen User should redirected to Home page
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_a_l_i_d_a_t_e_ _b_a_c_k_ _t_o_ _p_l_a_n_ _b_u_t_t_o_n_
  • Subscription page validation Jul 4, 2025 05:25:58 PM Fail
    check_circle cancel clear
    00 07 33.236
    cancel Scenario: Verify Daily Meal Plan availability
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 46.947
    check_circle Scenario: Verify Weekly Meal Plan availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Weekly Meal Plan should be available only in Premium
    00 06 38.452
    cancel Scenario: Verify Personalized Exercise Plan availability
    @PremiumUser_LogbookMedicalDosage
    • cancelGiven User is in the homepage
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _P_e_r_s_o_n_a_l_i_z_e_d_ _E_x_e_r_c_i_s_e_ _P_l_a_n_ _a_v_a_i_l_a_b_i_l_i_t_y_
    00 02 13.618
    check_circle Scenario: Verify 10-Day Quick Reversal Plan availability
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen 10-Day Quick Reversal Plan should be available only in Premium
    00 02 09.023
    check_circle Scenario: Verify 30-Day Blood Sugar Reduction Plan
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen 30-Day Blood Sugar Reduction Plan should be available only in Premium
    00 02 14.320
    check_circle Scenario: Verify Glucose Level Graph availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Both Free and Premium should show Glucose Level Graph as available
    00 01 55.663
    check_circle Scenario: Verify BMI Calculation availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Both Free and Premium should show BMI Calculation as available
    00 01 49.248
    check_circle Scenario: Verify Downloadable Meal Plan PDF availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Downloadable Meal Plan PDF should be available only in Premium
    00 02 29.298
    check_circle Scenario: Verify Reminders availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Reminders should be available only in Premium
    00 02 27.779
    check_circle Scenario: Verify Continue free button is visible
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen The "Continue free" button should be visible
    00 02 26.976
    cancel Scenario: Verify Upgrade to Premium button is visible
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen The "Upgrade to Premium" button should be visible
    • cancelhooks.Hooks.quitBrowser()
    00 02 41.614
    check_circle Scenario: Verify Free Account label
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen It should display "Free Account"
    00 02 38.925
    check_circle Scenario: Verify Premium Account label
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen It should display "Premium Account"
    00 02 15.739
    check_circle Scenario: Verify unavailable features are marked with gray X
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Features not included should have gray X icons
    00 02 19.827
    check_circle Scenario: Verify available features are marked with purple tick
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen All included features should have purple checkmarks
    00 02 17.739
    check_circle Scenario: Verify total number of features listed
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen It should list exactly 9 features
    00 07 17.157
    cancel Scenario: Verify position of Continue free button
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 16.617
    cancel Scenario: Verify position of Upgrade to Premium button
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 16.585
    cancel Scenario: Verify terms and conditions text is visible
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 38.136
    check_circle Scenario: Verify upgrade message header is displayed
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen It should show the text “Upgrade to premium for complete diabetes management”
    00 07 06.783
    cancel Scenario: Verify visual separation between Free and Premium plans
    @PremiumUser_LogbookPhysicalActivity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Verification on button navigation in home page Jul 4, 2025 05:28:09 PM Fail
    check_circle cancel clear
    00 02 12.763
    check_circle Scenario: Verify user able to download weekly plan
    • check_circleGiven User logged onto the application
    • check_circleGiven User is in home page
    • check_circleWhen User clicks Weekly plan
    • check_circleThen User should get pdf download of weekly plan
    00 03 19.189
    cancel Scenario: Verify the navigation of Blood Glucose button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on Blood glucose button
    • cancelThen User should redirect to Blood Glucose popup window
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 04 09.886
    cancel Scenario: Verify the navigation of Physical Activity button
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on physical activity button
    • cancelThen User should redirect to physical activity popup window
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 57.394
    cancel Scenario: Verify the navigation of Food Intake button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on food intake button
    • cancelThen User should redirect to food intake popup window
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _F_o_o_d_ _I_n_t_a_k_e_ _b_u_t_t_o_n_
    00 02 23.838
    cancel Scenario: Verify the navigation of Medication button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on medication button
    • cancelThen User should redirect to medication popup window
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _M_e_d_i_c_a_t_i_o_n_ _b_u_t_t_o_n_
    00 03 00.341
    cancel Scenario: Verify the navigation of log button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks log button
    • cancelThen User should redirected to dashboard page
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _l_o_g_ _b_u_t_t_o_n_
  • Subscription page validation Jul 4, 2025 05:28:45 PM Fail
    check_circle cancel clear
    00 02 10.645
    check_circle Scenario: Verify Daily Meal Plan availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Both Free and Premium should show Daily Meal Plan as available
    00 02 07.890
    check_circle Scenario: Verify Weekly Meal Plan availability
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Weekly Meal Plan should be available only in Premium
    00 01 44.944
    check_circle Scenario: Verify Personalized Exercise Plan availability
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Personalized Exercise Plan should be available only in Premium
    00 02 40.835
    check_circle Scenario: Verify 10-Day Quick Reversal Plan availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen 10-Day Quick Reversal Plan should be available only in Premium
    00 02 31.650
    check_circle Scenario: Verify 30-Day Blood Sugar Reduction Plan
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen 30-Day Blood Sugar Reduction Plan should be available only in Premium
    00 07 52.010
    cancel Scenario: Verify Glucose Level Graph availability
    • cancelGiven User is in the homepage
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 21.763
    check_circle Scenario: Verify BMI Calculation availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Both Free and Premium should show BMI Calculation as available
    00 02 26.101
    check_circle Scenario: Verify Downloadable Meal Plan PDF availability
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Downloadable Meal Plan PDF should be available only in Premium
    00 02 04.925
    check_circle Scenario: Verify Reminders availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Reminders should be available only in Premium
    00 01 53.579
    check_circle Scenario: Verify Continue free button is visible
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen The "Continue free" button should be visible
    00 08 02.163
    cancel Scenario: Verify Upgrade to Premium button is visible
    • cancelGiven User is in the homepage
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 17.736
    cancel Scenario: Verify Free Account label
    @PremiumUser_LogbookBloodGlucoseTracker
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 12.558
    cancel Scenario: Verify Premium Account label
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 06 51.035
    cancel Scenario: Verify unavailable features are marked with gray X
    @PremiumUser_LogbookPhysicalActivity
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 06 48.759
    cancel Scenario: Verify available features are marked with purple tick
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 06 46.753
    cancel Scenario: Verify total number of features listed
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 06 44.829
    cancel Scenario: Verify position of Continue free button
    @PremiumUser_LogbookLogReview
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 37.358
    check_circle Scenario: Verify position of Upgrade to Premium button
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen "Upgrade to Premium" button should appear
    00 01 51.371
    check_circle Scenario: Verify terms and conditions text is visible
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Terms & Conditions and Privacy Policy text should be visible
    00 01 22.995
    check_circle Scenario: Verify upgrade message header is displayed
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen It should show the text “Upgrade to premium for complete diabetes management”
    00 01 33.356
    check_circle Scenario: Verify visual separation between Free and Premium plans
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen The Free and Premium plans should be displayed side-by-side in clearly separated columns
  • Verification on button navigation in home page Jul 4, 2025 05:30:25 PM Fail
    check_circle cancel clear
    00 02 35.857
    check_circle Scenario: Verify user able to download weekly plan
    • check_circleGiven User logged onto the application
    • check_circleGiven User is in home page
    • check_circleWhen User clicks Weekly plan
    • check_circleThen User should get pdf download of weekly plan
    00 02 56.714
    cancel Scenario: Verify the navigation of Physical Activity button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on physical activity button
    • cancelThen User should redirect to physical activity popup window
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _P_h_y_s_i_c_a_l_ _A_c_t_i_v_i_t_y_ _b_u_t_t_o_n_
    00 04 11.080
    cancel Scenario: Verify the navigation of Blood Glucose button
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on Blood glucose button
    • cancelThen User should redirect to Blood Glucose popup window
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 03 26.860
    cancel Scenario: Verify the navigation of Food Intake button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on food intake button
    • cancelThen User should redirect to food intake popup window
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _F_o_o_d_ _I_n_t_a_k_e_ _b_u_t_t_o_n_
    00 03 05.335
    cancel Scenario: Verify the navigation of Medication button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks on medication button
    • cancelThen User should redirect to medication popup window
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _t_h_e_ _n_a_v_i_g_a_t_i_o_n_ _o_f_ _M_e_d_i_c_a_t_i_o_n_ _b_u_t_t_o_n_
    00 03 27.423
    cancel Scenario: Verify the navigation of log button
    • check_circleGiven User logged onto the application
    • check_circleWhen User clicks log button
    • cancelThen User should redirected to dashboard page
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • Subscription page validation Jul 4, 2025 05:31:04 PM Fail
    check_circle cancel clear
    00 07 42.802
    cancel Scenario: Verify Daily Meal Plan availability
    • cancelGiven User is in the homepage
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 14.883
    cancel Scenario: Verify Weekly Meal Plan availability
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 02.753
    cancel Scenario: Verify Personalized Exercise Plan availability
    @PremiumUser_Exercise
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 42.521
    check_circle Scenario: Verify 10-Day Quick Reversal Plan availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen 10-Day Quick Reversal Plan should be available only in Premium
    00 01 47.033
    check_circle Scenario: Verify 30-Day Blood Sugar Reduction Plan
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen 30-Day Blood Sugar Reduction Plan should be available only in Premium
    00 02 01.269
    check_circle Scenario: Verify Glucose Level Graph availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Both Free and Premium should show Glucose Level Graph as available
    00 01 46.591
    check_circle Scenario: Verify BMI Calculation availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Both Free and Premium should show BMI Calculation as available
    00 01 29.120
    check_circle Scenario: Verify Downloadable Meal Plan PDF availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Downloadable Meal Plan PDF should be available only in Premium
    00 01 36.744
    check_circle Scenario: Verify Reminders availability
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Reminders should be available only in Premium
    00 01 28.763
    check_circle Scenario: Verify Continue free button is visible
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen The "Continue free" button should be visible
    00 07 37.949
    cancel Scenario: Verify Upgrade to Premium button is visible
    • cancelGiven User is in the homepage
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 44.219
    check_circle Scenario: Verify Free Account label
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen It should display "Free Account"
    00 01 19.910
    check_circle Scenario: Verify Premium Account label
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen It should display "Premium Account"
    00 01 41.985
    check_circle Scenario: Verify unavailable features are marked with gray X
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Features not included should have gray X icons
    00 01 36.729
    check_circle Scenario: Verify available features are marked with purple tick
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen All included features should have purple checkmarks
    00 01 39.464
    check_circle Scenario: Verify total number of features listed
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen It should list exactly 9 features
    00 01 43.448
    check_circle Scenario: Verify position of Continue free button
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen "Continue free" button should appear
    00 01 43.162
    check_circle Scenario: Verify position of Upgrade to Premium button
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen "Upgrade to Premium" button should appear
    00 01 22.999
    check_circle Scenario: Verify terms and conditions text is visible
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen Terms & Conditions and Privacy Policy text should be visible
    00 01 28.470
    check_circle Scenario: Verify upgrade message header is displayed
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen It should show the text “Upgrade to premium for complete diabetes management”
    00 01 28.301
    check_circle Scenario: Verify visual separation between Free and Premium plans
    • check_circleGiven User is in the homepage
    • check_circleWhen User clicks view full plan button in homepage
    • check_circleThen The Free and Premium plans should be displayed side-by-side in clearly separated columns
  • Post-Onboarding Navigation and Upgrade Flow Jul 4, 2025 05:33:14 PM Fail
    check_circle cancel clear
    00 07 04.194
    cancel Scenario: Verify user able to go to subscription payment screen
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 07 02.254
    cancel Scenario: Verify title of Upgrade screen
    @PremiumUser_LogbookMedicalDosage
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 06 53.781
    cancel Scenario: Verify sub text
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 02 06.293
    check_circle Scenario: Verify the presence of "premium features"
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see text "premium features"
    00 06 47.079
    cancel Scenario: verify the description for premium feature
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 32.367
    check_circle Scenario: verify the presence of subscription price
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "$9.99/month"
    00 02 02.243
    check_circle Scenario: verify the presence of cancel anytime text
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see cancel anytime text below the pricing details
    00 01 41.732
    check_circle Scenario: Verify the presence of "Card Number"
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see heading "Card Number"
    00 01 28.620
    check_circle Scenario: Verify the presence of fields in payment
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see card number, expiration , cvv field
    00 01 16.405
    check_circle Scenario: Verify presence of payment button
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "Pay $9.99 USD" button
    00 02 09.765
    check_circle Scenario: Verify terms and renewal message
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see terms of service and auto-renewal notice
    00 01 14.666
    check_circle Scenario: Verify the presence of terms and auto-renewal note
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "By completing this purchase, you agree to our Terms of Service and Privacy Policy. Your subscription will automatically renew each month until cancelled."
    00 01 26.723
    cancel Scenario: Verify user able to go to home page
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is in upgrade page
    • check_circleWhen user clicks the "Continue free" button
    • cancelThen User should be redirected to the home page
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _a_b_l_e_ _t_o_ _g_o_ _t_o_ _h_o_m_e_ _p_a_g_e_
  • Post-Onboarding Navigation and Upgrade Flow Jul 4, 2025 05:36:37 PM Fail
    check_circle cancel clear
    00 02 09.368
    cancel Scenario: Verify user able to go to subscription payment screen
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • cancelThen User should be redirected to the subscription payment screen
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _a_b_l_e_ _t_o_ _g_o_ _t_o_ _s_u_b_s_c_r_i_p_t_i_o_n_ _p_a_y_m_e_n_t_ _s_c_r_e_e_n_
    00 01 47.292
    check_circle Scenario: Verify title of Upgrade screen
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen Page title should be "Upgrade to Premium"
    00 01 03.878
    check_circle Scenario: Verify the presence of "premium features"
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see text "premium features"
    00 01 04.487
    check_circle Scenario: Verify sub text
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "Get personalized insights and advanced features to better manage your diabetes."
    00 01 02.187
    check_circle Scenario: verify the description for premium feature
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see text "✓Personalized meal plans,✓Advanced analytics,✓Priority support"
    00 00 43.265
    check_circle Scenario: verify the presence of subscription price
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "$9.99/month"
    00 00 48.227
    check_circle Scenario: verify the presence of cancel anytime text
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see cancel anytime text below the pricing details
    00 00 35.355
    check_circle Scenario: Verify the presence of "Card Number"
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see heading "Card Number"
    00 00 36.183
    check_circle Scenario: Verify the presence of fields in payment
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see card number, expiration , cvv field
    00 01 19.068
    check_circle Scenario: Verify presence of payment button
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "Pay $9.99 USD" button
    00 01 15.692
    check_circle Scenario: Verify terms and renewal message
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see terms of service and auto-renewal notice
    00 01 17.568
    check_circle Scenario: Verify the presence of terms and auto-renewal note
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "By completing this purchase, you agree to our Terms of Service and Privacy Policy. Your subscription will automatically renew each month until cancelled."
    00 01 22.278
    cancel Scenario: Verify user able to go to home page
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is in upgrade page
    • check_circleWhen user clicks the "Continue free" button
    • cancelThen User should be redirected to the home page
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _a_b_l_e_ _t_o_ _g_o_ _t_o_ _h_o_m_e_ _p_a_g_e_
  • Post-Onboarding Navigation and Upgrade Flow Jul 4, 2025 05:37:41 PM Fail
    check_circle cancel clear
    00 01 57.905
    cancel Scenario: Verify user able to go to subscription payment screen
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • cancelThen User should be redirected to the subscription payment screen
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _a_b_l_e_ _t_o_ _g_o_ _t_o_ _s_u_b_s_c_r_i_p_t_i_o_n_ _p_a_y_m_e_n_t_ _s_c_r_e_e_n_
    00 01 16.230
    check_circle Scenario: Verify title of Upgrade screen
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen Page title should be "Upgrade to Premium"
    00 01 03.483
    check_circle Scenario: Verify sub text
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "Get personalized insights and advanced features to better manage your diabetes."
    00 01 00.957
    check_circle Scenario: Verify the presence of "premium features"
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see text "premium features"
    00 00 59.752
    check_circle Scenario: verify the description for premium feature
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see text "✓Personalized meal plans,✓Advanced analytics,✓Priority support"
    00 00 57.196
    check_circle Scenario: verify the presence of subscription price
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "$9.99/month"
    00 01 30.079
    check_circle Scenario: verify the presence of cancel anytime text
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see cancel anytime text below the pricing details
    00 00 45.613
    check_circle Scenario: Verify the presence of "Card Number"
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see heading "Card Number"
    00 00 45.316
    check_circle Scenario: Verify the presence of fields in payment
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see card number, expiration , cvv field
    00 00 38.953
    check_circle Scenario: Verify presence of payment button
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "Pay $9.99 USD" button
    00 00 38.420
    check_circle Scenario: Verify terms and renewal message
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see terms of service and auto-renewal notice
    00 02 42.778
    check_circle Scenario: Verify the presence of terms and auto-renewal note
    • check_circleGiven User is in upgrade page
    • check_circleWhen User clicks the "Upgrade to Premium" button
    • check_circleThen User should see "By completing this purchase, you agree to our Terms of Service and Privacy Policy. Your subscription will automatically renew each month until cancelled."
    00 00 45.774
    cancel Scenario: Verify user able to go to home page
    • check_circleGiven User is in upgrade page
    • check_circleWhen user clicks the "Continue free" button
    • cancelThen User should be redirected to the home page
    • check_circlehooks.Hooks.tearDown(io.cucumber.java.Scenario)
      _V_e_r_i_f_y_ _u_s_e_r_ _a_b_l_e_ _t_o_ _g_o_ _t_o_ _h_o_m_e_ _p_a_g_e_
  • Login Page UI Verification Jul 4, 2025 05:40:18 PM Pass
    check_circle cancel clear
    00 00 59.097
    check_circle Scenario: Verify login form header is played
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see Welcome back heading
    00 01 02.215
    check_circle Scenario: Verify sub text of the header
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see Sign in to your account or create a new one
    00 00 54.258
    check_circle Scenario: Verify the presence of close button
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see close button at the right corner
    00 00 58.884
    check_circle Scenario: Verify the presence of close button
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see an input field to enter email
    00 01 00.859
    check_circle Scenario: Verify email input field is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see an input field to enter email
    00 01 00.425
    check_circle Scenario: Validate placeholder text in email field
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see text Enter Email in email field placeholder
    00 00 55.791
    check_circle Scenario: Verify Continue with Email button is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see a Continue with email button
    00 00 51.375
    check_circle Scenario: Verify Continue with Email button is enabled
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see Continue with email button to be enabled
    00 01 21.452
    check_circle Scenario: Verify Continue with Google button is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see a Continue with Google button
    00 00 53.116
    check_circle Scenario: Verify OR separator is visible
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see an OR separator
    00 01 15.484
    check_circle Scenario: Verify Terms and Privacy message is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see By continuing you agree to our T&C and Privacy
  • Login Page UI Verification Jul 4, 2025 05:40:18 PM Fail
    check_circle cancel clear
    00 01 03.782
    check_circle Scenario: Verify login form header is played
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see Welcome back heading
    00 00 57.738
    check_circle Scenario: Verify email input field is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see an input field to enter email
    00 06 42.806
    cancel Scenario: Verify the presence of close button
    • cancelhooks.Hooks.launchbrowser()
    • cancelhooks.Hooks.tearDown(io.cucumber.java.Scenario)
    00 01 08.107
    check_circle Scenario: Validate placeholder text in email field
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see text Enter Email in email field placeholder
    00 00 59.995
    check_circle Scenario: Verify the presence of close button
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see an input field to enter email
    00 00 55.191
    check_circle Scenario: Verify Continue with Email button is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see a Continue with email button
    00 01 01.551
    check_circle Scenario: Verify sub text of the header
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see Sign in to your account or create a new one
    00 00 57.253
    check_circle Scenario: Verify Continue with Email button is enabled
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see Continue with email button to be enabled
    00 00 58.670
    check_circle Scenario: Verify Continue with Google button is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see a Continue with Google button
    00 00 55.040
    check_circle Scenario: Verify OR separator is visible
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see an OR separator
    00 01 24.969
    check_circle Scenario: Verify Terms and Privacy message is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see By continuing you agree to our T&C and Privacy
  • Login Page UI Verification Jul 4, 2025 05:40:19 PM Pass
    check_circle cancel clear
    00 00 58.612
    check_circle Scenario: Verify login form header is played
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see Welcome back heading
    00 00 57.669
    check_circle Scenario: Verify sub text of the header
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see Sign in to your account or create a new one
    00 00 48.888
    check_circle Scenario: Verify the presence of close button
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see close button at the right corner
    00 01 02.141
    check_circle Scenario: Verify the presence of close button
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see an input field to enter email
    00 00 56.196
    check_circle Scenario: Verify email input field is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see an input field to enter email
    00 00 50.157
    check_circle Scenario: Validate placeholder text in email field
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see text Enter Email in email field placeholder
    00 01 33.182
    check_circle Scenario: Verify Continue with Email button is displayed
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see a Continue with email button
    00 00 56.248
    check_circle Scenario: Verify Continue with Email button is enabled
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see Continue with email button to be enabled
    00 01 35.770
    check_circle Scenario: Verify Continue with Google button is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see a Continue with Google button
    00 01 24.351
    check_circle Scenario: Verify OR separator is visible
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see an OR separator
    00 01 15.896
    check_circle Scenario: Verify Terms and Privacy message is displayed
    • check_circleGiven User is on SweetBalance homepage
    • check_circleWhen User clicks on Login link
    • check_circleThen User should see By continuing you agree to our T&C and Privacy
  • Login page field and functional Validation Jul 4, 2025 05:41:19 PM Pass
    check_circle cancel clear
    00 01 34.934
    check_circle Scenario: Verify email input accepts valid existing email
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should get password field
    00 01 51.880
    check_circle Scenario: Verify email input rejects invalid email
    • check_circleGiven User is on the login page
    • check_circleWhen User enters an invalid email
    • check_circleThen Email field should show validation error
    00 01 32.735
    check_circle Scenario: Verify password field in login page
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see Sign in button
    00 01 26.650
    check_circle Scenario: Verify sub text
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see email id in sub text
    00 01 19.836
    check_circle Scenario: Verify presence of forgot password link
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see Forgot password? link
    00 01 17.888
    check_circle Scenario: Verify presence of placeholder in password field
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see text Enter your password as placeholder in password field
    00 01 04.317
    check_circle Scenario: Verify password input accepts valid existing user
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks sign in after entering email and password
    • check_circleThen User should be navigated to home page
    00 00 59.123
    check_circle Scenario: Verify email input accepts valid new email
    • check_circleGiven User is on the login page
    • check_circleWhen Unregistered user clicks continue with email button after entering a valid new email
    • check_circleThen User should get Complete your profile form
  • Login page field and functional Validation Jul 4, 2025 05:41:25 PM Pass
    check_circle cancel clear
    00 01 31.283
    check_circle Scenario: Verify email input accepts valid existing email
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should get password field
    00 01 22.496
    check_circle Scenario: Verify email input rejects invalid email
    • check_circleGiven User is on the login page
    • check_circleWhen User enters an invalid email
    • check_circleThen Email field should show validation error
    00 01 24.335
    check_circle Scenario: Verify password field in login page
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see Sign in button
    00 01 19.796
    check_circle Scenario: Verify sub text
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see email id in sub text
    00 01 19.423
    check_circle Scenario: Verify presence of forgot password link
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see Forgot password? link
    00 01 03.056
    check_circle Scenario: Verify presence of placeholder in password field
    @PremiumUser_LogbookBloodGlucoseTracker
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see text Enter your password as placeholder in password field
    00 00 43.425
    check_circle Scenario: Verify password input accepts valid existing user
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks sign in after entering email and password
    • check_circleThen User should be navigated to home page
    00 00 39.856
    check_circle Scenario: Verify email input accepts valid new email
    • check_circleGiven User is on the login page
    • check_circleWhen Unregistered user clicks continue with email button after entering a valid new email
    • check_circleThen User should get Complete your profile form
  • Login page field and functional Validation Jul 4, 2025 05:41:32 PM Pass
    check_circle cancel clear
    00 01 23.444
    check_circle Scenario: Verify email input accepts valid existing email
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should get password field
    00 01 15.693
    check_circle Scenario: Verify email input rejects invalid email
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is on the login page
    • check_circleWhen User enters an invalid email
    • check_circleThen Email field should show validation error
    00 01 19.449
    check_circle Scenario: Verify password field in login page
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see Sign in button
    00 01 17.430
    check_circle Scenario: Verify sub text
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see email id in sub text
    00 01 24.420
    check_circle Scenario: Verify presence of forgot password link
    @PremiumUser_LogbookLogReview
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see Forgot password? link
    00 00 59.459
    check_circle Scenario: Verify presence of placeholder in password field
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks continue with email button after entering a valid existing email
    • check_circleThen User should see text Enter your password as placeholder in password field
    00 00 33.903
    check_circle Scenario: Verify password input accepts valid existing user
    • check_circleGiven User is on the login page
    • check_circleWhen Registered user clicks sign in after entering email and password
    • check_circleThen User should be navigated to home page
    00 00 29.034
    check_circle Scenario: Verify email input accepts valid new email
    @PremiumUser_LogbookPhysicalActivity
    • check_circleGiven User is on the login page
    • check_circleWhen Unregistered user clicks continue with email button after entering a valid new email
    • check_circleThen User should get Complete your profile form
search Search
  • @physicalActity 20 56
    Passed: 20 Failed: 56
    Timestamp TestName Status
    Jul 4, 2025 04:57:14 PM Verify title in Food Intake form Fail
    Jul 4, 2025 05:00:09 PM Verify subtext in form Pass
    Jul 4, 2025 05:00:13 PM Verify presence of 4 tabs Fail
    Jul 4, 2025 05:00:14 PM Verify title in Food Intake form Fail
    Jul 4, 2025 05:00:14 PM Verify title in Food Intake form Fail
    Jul 4, 2025 05:00:18 PM Verify fields in Food Intake form Fail
    Jul 4, 2025 05:00:27 PM Verify subtext in form Pass
    Jul 4, 2025 05:00:49 PM Verify presence of 4 tabs Fail
    Jul 4, 2025 05:00:49 PM Verify subtext in form Pass
    Jul 4, 2025 05:00:50 PM Verify default meal tab Fail
    Jul 4, 2025 05:01:18 PM Verify fields in Food Intake form Fail
    Jul 4, 2025 05:01:24 PM Verify input field for food name Pass
    Jul 4, 2025 05:01:28 PM Verify default meal tab Pass
    Jul 4, 2025 05:01:40 PM Verify presence of 4 tabs Fail
    Jul 4, 2025 05:01:43 PM Verify placeholder in food name field Pass
    Jul 4, 2025 05:01:51 PM Verify input field for food name Fail
    Jul 4, 2025 05:01:52 PM Verify dropdown for Serving Size Fail
    Jul 4, 2025 05:01:53 PM Verify options in Serving Size Fail
    Jul 4, 2025 05:01:53 PM Verify default value in Serving Size Fail
    Jul 4, 2025 05:01:55 PM Verify placeholder in food name field Fail
    Jul 4, 2025 05:01:56 PM Verify input field for food name Fail
    Jul 4, 2025 05:01:56 PM Verify calculator icon in calorie field Fail
    Jul 4, 2025 05:01:56 PM Verify input field for calorie Fail
    Jul 4, 2025 05:01:56 PM Verify default meal tab Fail
    Jul 4, 2025 05:01:56 PM Verify fields in Food Intake form Fail
    Jul 4, 2025 05:01:59 PM Verify placeholder in food name field Fail
    Jul 4, 2025 05:02:29 PM Verify default value in Serving Size Pass
    Jul 4, 2025 05:02:29 PM Verify dropdown for Serving Size Fail
    Jul 4, 2025 05:02:29 PM Verify default value in Serving Size Pass
    Jul 4, 2025 05:02:29 PM Verify dropdown for Serving Size Fail
    Jul 4, 2025 05:02:29 PM Verify options in Serving Size Fail
    Jul 4, 2025 05:02:30 PM Verify options in Serving Size Fail
    Jul 4, 2025 05:02:41 PM Verify calculator icon in calorie field Fail
    Jul 4, 2025 05:02:44 PM Verify placeholder in calorie field Fail
    Jul 4, 2025 05:02:44 PM Verify calculator icon in calorie field Fail
    Jul 4, 2025 05:02:45 PM Verify input field for calorie Fail
    Jul 4, 2025 05:02:45 PM Verify helper text under calorie field Fail
    Jul 4, 2025 05:02:56 PM Verify input field for calorie Fail
    Jul 4, 2025 05:03:00 PM Verify date picker after popup Fail
    Jul 4, 2025 05:03:01 PM Verify placeholder in calorie field Fail
    Jul 4, 2025 05:03:21 PM Verify helper text under calorie field Pass
    Jul 4, 2025 05:03:23 PM Verify default value in Date field Fail
    Jul 4, 2025 05:03:49 PM Verify input for notes Fail
    Jul 4, 2025 05:03:50 PM Verify date picker after popup Fail
    Jul 4, 2025 05:04:10 PM Verify placeholder in calorie field Fail
    Jul 4, 2025 05:04:53 PM Verify helper text under calorie field Fail
    Jul 4, 2025 05:04:53 PM Verify default value in Date field Fail
    Jul 4, 2025 05:05:45 PM Verify input for notes Pass
    Jul 4, 2025 05:05:45 PM Verify default value in Date field Fail
    Jul 4, 2025 05:05:45 PM Verify date picker after popup Fail
    Jul 4, 2025 05:05:46 PM Verify placeholder in notes Pass
    Jul 4, 2025 05:06:30 PM Verify placeholder in notes Pass
    Jul 4, 2025 05:06:30 PM Verify save food entry button Fail
    Jul 4, 2025 05:06:40 PM Verify save food entry button Fail
    Jul 4, 2025 05:06:42 PM Verify input for notes Fail
    Jul 4, 2025 05:07:55 PM Verify pre-meal title is shown before main meal Fail
    Jul 4, 2025 05:08:08 PM Verify placeholder in notes Fail
    Jul 4, 2025 05:08:53 PM Verify save food entry button Pass
    Jul 4, 2025 05:09:03 PM Verify the presence of Sub title "Main-Meal" Fail
    Jul 4, 2025 05:11:16 PM Validate the indicator for lunch main-meal Fail
    Jul 4, 2025 05:11:34 PM Verify the time in main-lunch Fail
    Jul 4, 2025 05:13:02 PM Verify the time in main-lunch Fail
    Jul 4, 2025 05:14:21 PM Validate the indicator for breakfast main-meal Fail
    Jul 4, 2025 05:15:44 PM Verify the time in main-breakfast Fail
    Jul 4, 2025 05:16:01 PM Verify the presence of ⚠️ Partially Completed button Pass
    Jul 4, 2025 05:17:08 PM Verify color change of completed button Fail
    Jul 4, 2025 05:17:29 PM Verify each meal calorie detail on the right side Pass
    Jul 4, 2025 05:19:43 PM Verify meal section button in View Plan page Fail
    Jul 4, 2025 05:20:30 PM Verify sub-title in nutrition flex card Pass
    Jul 4, 2025 05:22:31 PM Verify pre meal preparation in view full plan Pass
    Jul 4, 2025 05:23:01 PM Verify presence of Back to Plan button Fail
    Jul 4, 2025 05:23:18 PM Verify the first option text Fail
    Jul 4, 2025 05:24:16 PM Verify Diabetes Management Tips heading Pass
    Jul 4, 2025 05:25:14 PM Verify pre-meal includes description under the item name Fail
    Jul 4, 2025 05:25:44 PM Verify meal preparation Pass
    Jul 4, 2025 05:28:15 PM Verify Nutrients information Pass
  • @FoodIntake 3
    Failed: 3
    Timestamp TestName Status
    Jul 4, 2025 04:57:14 PM Verify title in Food Intake form Fail
    Jul 4, 2025 05:00:14 PM Verify title in Food Intake form Fail
    Jul 4, 2025 05:00:14 PM Verify title in Food Intake form Fail
  • @PremiumUser_LogbookBloodGlucoseTracker 52 42
    Passed: 52 Failed: 42
    Timestamp TestName Status
    Jul 4, 2025 04:37:04 PM Verify presence of Blood Glucose Tracker section Pass
    Jul 4, 2025 04:37:04 PM Verify title of Blood Glucose tracker section Fail
    Jul 4, 2025 04:37:34 PM Verify colour codes for Fasting Pass
    Jul 4, 2025 04:37:54 PM Verify Fasting glucose type range displayed Pass
    Jul 4, 2025 04:37:58 PM Verify colour codes for Pre-Meal Pass
    Jul 4, 2025 04:38:42 PM Verify pre-meal glucose type range displayed Fail
    Jul 4, 2025 04:38:44 PM Verify colour codes for Post-Meal Fail
    Jul 4, 2025 04:39:07 PM Verify presence of Blood Glucose Tracker section Fail
    Jul 4, 2025 04:39:10 PM Verify presence of Blood Glucose Tracker section Fail
    Jul 4, 2025 04:39:11 PM Verify title of Blood Glucose tracker section Fail
    Jul 4, 2025 04:39:12 PM Verify Post-meal glucose type range displayed Fail
    Jul 4, 2025 04:39:16 PM Verify colour codes for Bedtime Pass
    Jul 4, 2025 04:39:24 PM Verify bedtime glucose type range displayed Pass
    Jul 4, 2025 04:39:24 PM Verify colour codes for Fasting Pass
    Jul 4, 2025 04:39:46 PM Verify title of Blood Glucose tracker section Fail
    Jul 4, 2025 04:39:59 PM Verify Fasting glucose type range displayed Fail
    Jul 4, 2025 04:40:02 PM Verify last 7 days are displayed on X-axis Pass
    Jul 4, 2025 04:40:09 PM Verify Y-axis starts at 70 in glucose chart Pass
    Jul 4, 2025 04:40:33 PM Verify colour codes for Pre-Meal Pass
    Jul 4, 2025 04:40:33 PM Verify Y-axis ends at 180 in glucose chart Pass
    Jul 4, 2025 04:40:56 PM Verify colour codes for Fasting Pass
    Jul 4, 2025 04:40:57 PM Verify Fasting glucose type range displayed Pass
    Jul 4, 2025 04:40:57 PM Verify colour codes for Pre-Meal Pass
    Jul 4, 2025 04:40:58 PM Verify pre-meal glucose type range displayed Pass
    Jul 4, 2025 04:41:00 PM Verify pre-meal glucose type range displayed Pass
    Jul 4, 2025 04:41:10 PM Verify colour codes for Post-Meal Pass
    Jul 4, 2025 04:41:19 PM Verify Post-meal glucose type range displayed Pass
    Jul 4, 2025 04:41:21 PM Verify colour codes for Post-Meal Pass
    Jul 4, 2025 04:41:41 PM Verify Post-meal glucose type range displayed Pass
    Jul 4, 2025 04:41:41 PM Verify colour codes for Bedtime Pass
    Jul 4, 2025 04:41:41 PM Verify colour codes for Bedtime Pass
    Jul 4, 2025 04:41:41 PM Verify bedtime glucose type range displayed Pass
    Jul 4, 2025 04:41:42 PM Verify last 7 days are displayed on X-axis Pass
    Jul 4, 2025 04:41:48 PM Verify bedtime glucose type range displayed Pass
    Jul 4, 2025 04:41:53 PM Verify last 7 days are displayed on X-axis Pass
    Jul 4, 2025 04:41:55 PM Verify Y-axis starts at 70 in glucose chart Pass
    Jul 4, 2025 04:42:04 PM Verify Y-axis ends at 180 in glucose chart Pass
    Jul 4, 2025 04:42:07 PM Verify Y-axis starts at 70 in glucose chart Pass
    Jul 4, 2025 04:42:14 PM Verify Y-axis ends at 180 in glucose chart Pass
    Jul 4, 2025 04:46:17 PM Verify the default value in datepicker Pass
    Jul 4, 2025 04:46:22 PM Verify display of empty chart for no activity log Pass
    Jul 4, 2025 04:46:27 PM Verify the daily average value for no activity log Pass
    Jul 4, 2025 04:47:13 PM Verify the default value in datepicker Pass
    Jul 4, 2025 04:47:22 PM Verify presence of iframe Fail
    Jul 4, 2025 04:47:28 PM Verify heading in iframe Fail
    Jul 4, 2025 04:50:18 PM Verify the presence of Cancel button Pass
    Jul 4, 2025 04:50:23 PM Verify Add Medication button Pass
    Jul 4, 2025 04:52:35 PM Verify text block for Notes Fail
    Jul 4, 2025 04:53:00 PM Add medication with invalid dosage Fail
    Jul 4, 2025 04:53:00 PM Verify checkbox for Take with food Fail
    Jul 4, 2025 04:54:16 PM Verify scheduled time for three times daily Fail
    Jul 4, 2025 04:54:16 PM Add medication with valid data Fail
    Jul 4, 2025 04:54:44 PM Verify today's date is highlighted Fail
    Jul 4, 2025 04:57:10 PM Mark medication as taken Fail
    Jul 4, 2025 04:58:15 PM Remove added medication Fail
    Jul 4, 2025 05:00:09 PM Verify subtext in form Pass
    Jul 4, 2025 05:00:49 PM Verify subtext in form Pass
    Jul 4, 2025 05:01:24 PM Verify input field for food name Pass
    Jul 4, 2025 05:01:56 PM Verify fields in Food Intake form Fail
    Jul 4, 2025 05:02:30 PM Verify options in Serving Size Fail
    Jul 4, 2025 05:03:00 PM Verify date picker after popup Fail
    Jul 4, 2025 05:04:10 PM Verify placeholder in calorie field Fail
    Jul 4, 2025 05:06:39 PM Verify the presence of "Pre-meal" title in each meal section Fail
    Jul 4, 2025 05:06:40 PM Verify save food entry button Fail
    Jul 4, 2025 05:08:08 PM Verify placeholder in notes Fail
    Jul 4, 2025 05:09:05 PM Verify the presence of icon for main-meal Fail
    Jul 4, 2025 05:09:52 PM Verify the time format in each main-meal Fail
    Jul 4, 2025 05:11:54 PM Validate the indicator for snack main-meal Fail
    Jul 4, 2025 05:14:38 PM Verify the time in main-snack Fail
    Jul 4, 2025 05:15:39 PM Validate the indicator for snack main-meal Fail
    Jul 4, 2025 05:16:18 PM Verify navigation to View Full Meal Plan Fail
    Jul 4, 2025 05:17:05 PM Verify total calorie count from pre-meal and meal Fail
    Jul 4, 2025 05:17:06 PM Verify the presence of ❌ Not Completed button Pass
    Jul 4, 2025 05:21:14 PM Verify the title of the popup Fail
    Jul 4, 2025 05:21:15 PM Verify total calorie count from pre-meal and meal Pass
    Jul 4, 2025 05:23:38 PM Verify Nutrients information Fail
    Jul 4, 2025 05:23:46 PM Verify the first option text Fail
    Jul 4, 2025 05:25:55 PM Verify the navigation of log button Fail
    Jul 4, 2025 05:25:58 PM Verify nutrients list (Pre-meal portion) Fail
    Jul 4, 2025 05:28:42 PM Verify the navigation of Physical Activity button Fail
    Jul 4, 2025 05:30:25 PM Verify Continue free button is visible Pass
    Jul 4, 2025 05:30:55 PM Verify the navigation of Blood Glucose button Fail
    Jul 4, 2025 05:33:01 PM Verify Free Account label Fail
    Jul 4, 2025 05:33:01 PM Verify position of Continue free button Fail
    Jul 4, 2025 05:35:08 PM Verify Continue free button is visible Pass
    Jul 4, 2025 05:36:37 PM Verify position of Continue free button Pass
    Jul 4, 2025 05:38:22 PM Verify title of Upgrade screen Pass
    Jul 4, 2025 05:39:38 PM Verify the presence of "Card Number" Pass
    Jul 4, 2025 05:40:19 PM Verify the presence of close button Pass
    Jul 4, 2025 05:40:19 PM Verify sub text of the header Pass
    Jul 4, 2025 05:40:24 PM Verify the presence of close button Pass
    Jul 4, 2025 05:41:17 PM Verify Continue with Email button is displayed Pass
    Jul 4, 2025 05:41:19 PM Verify OR separator is visible Pass
    Jul 4, 2025 05:42:12 PM Verify presence of placeholder in password field Pass
  • @PremiumUser_LogbookLogReview 102 32
    Passed: 102 Failed: 32
    Timestamp TestName Status
    Jul 4, 2025 04:40:40 PM Verify the Title of Log review section Pass
    Jul 4, 2025 04:40:56 PM Verify table header in log review section Pass
    Jul 4, 2025 04:41:19 PM Verify log review displays last 7 days of date entries including today Pass
    Jul 4, 2025 04:41:19 PM Verify the display of date format Pass
    Jul 4, 2025 04:41:24 PM Verify the order of date Pass
    Jul 4, 2025 04:41:32 PM Verify the blood glucose value in log review section if there is no log Pass
    Jul 4, 2025 04:41:38 PM Verify the nutrient value in log review section if there is no log Pass
    Jul 4, 2025 04:41:52 PM Verify the physical activity value in log review section if there is no log Pass
    Jul 4, 2025 04:41:53 PM Verify the entries of Medication in log review section if there is no value Pass
    Jul 4, 2025 04:41:54 PM Verify the blood glucose entries in log review section if there is log Pass
    Jul 4, 2025 04:42:04 PM Verify the nutrient value entries in log review section if there is log Pass
    Jul 4, 2025 04:42:04 PM Verify the Title of Log review section Pass
    Jul 4, 2025 04:42:04 PM Verify the physical activity entries in log review section if there is log Pass
    Jul 4, 2025 04:42:05 PM Verify table header in log review section Pass
    Jul 4, 2025 04:42:06 PM Verify log review displays last 7 days of date entries including today Pass
    Jul 4, 2025 04:42:15 PM Verify the medication value in log review section if there is log Pass
    Jul 4, 2025 04:42:17 PM Verify the Title of Log review section Pass
    Jul 4, 2025 04:42:17 PM Verify the Title of Log review section Pass
    Jul 4, 2025 04:42:17 PM Verify table header in log review section Pass
    Jul 4, 2025 04:42:17 PM Verify the display of date format Pass
    Jul 4, 2025 04:42:18 PM Verify table header in log review section Pass
    Jul 4, 2025 04:42:18 PM Verify log review displays last 7 days of date entries including today Pass
    Jul 4, 2025 04:42:18 PM Verify the display of date format Pass
    Jul 4, 2025 04:42:18 PM Verify log review displays last 7 days of date entries including today Pass
    Jul 4, 2025 04:42:18 PM Verify the order of date Pass
    Jul 4, 2025 04:42:19 PM Verify the blood glucose value in log review section if there is no log Pass
    Jul 4, 2025 04:42:20 PM Verify the display of date format Pass
    Jul 4, 2025 04:42:20 PM Verify the order of date Pass
    Jul 4, 2025 04:42:23 PM Verify the order of date Pass
    Jul 4, 2025 04:42:33 PM Verify the blood glucose value in log review section if there is no log Pass
    Jul 4, 2025 04:42:33 PM Verify the nutrient value in log review section if there is no log Pass
    Jul 4, 2025 04:42:34 PM Verify the physical activity value in log review section if there is no log Pass
    Jul 4, 2025 04:42:37 PM Verify the entries of Medication in log review section if there is no value Pass
    Jul 4, 2025 04:42:38 PM Verify the blood glucose entries in log review section if there is log Pass
    Jul 4, 2025 04:42:38 PM Verify the blood glucose value in log review section if there is no log Pass
    Jul 4, 2025 04:42:51 PM Verify the nutrient value in log review section if there is no log Pass
    Jul 4, 2025 04:42:53 PM Verify the physical activity value in log review section if there is no log Pass
    Jul 4, 2025 04:42:53 PM Verify the nutrient value in log review section if there is no log Pass
    Jul 4, 2025 04:42:54 PM Verify the physical activity value in log review section if there is no log Pass
    Jul 4, 2025 04:42:55 PM Verify the entries of Medication in log review section if there is no value Pass
    Jul 4, 2025 04:42:56 PM Verify the entries of Medication in log review section if there is no value Pass
    Jul 4, 2025 04:42:57 PM Verify the nutrient value entries in log review section if there is log Pass
    Jul 4, 2025 04:42:57 PM Verify the blood glucose entries in log review section if there is log Pass
    Jul 4, 2025 04:42:57 PM Verify the nutrient value entries in log review section if there is log Pass
    Jul 4, 2025 04:42:58 PM Verify the blood glucose entries in log review section if there is log Pass
    Jul 4, 2025 04:42:58 PM Verify the physical activity entries in log review section if there is log Pass
    Jul 4, 2025 04:43:01 PM Verify the nutrient value entries in log review section if there is log Pass
    Jul 4, 2025 04:43:01 PM Verify the physical activity entries in log review section if there is log Pass
    Jul 4, 2025 04:43:02 PM Verify the medication value in log review section if there is log Pass
    Jul 4, 2025 04:43:17 PM Verify the physical activity entries in log review section if there is log Pass
    Jul 4, 2025 04:43:19 PM Verify the Title of Log review section Pass
    Jul 4, 2025 04:43:20 PM Verify table header in log review section Pass
    Jul 4, 2025 04:43:20 PM Verify the medication value in log review section if there is log Pass
    Jul 4, 2025 04:43:20 PM Verify log review displays last 7 days of date entries including today Pass
    Jul 4, 2025 04:43:21 PM Verify the medication value in log review section if there is log Pass
    Jul 4, 2025 04:43:21 PM Verify the display of date format Pass
    Jul 4, 2025 04:43:36 PM Verify the Title of Log review section Pass
    Jul 4, 2025 04:43:42 PM Verify table header in log review section Pass
    Jul 4, 2025 04:43:45 PM Verify the order of date Pass
    Jul 4, 2025 04:43:45 PM Verify log review displays last 7 days of date entries including today Pass
    Jul 4, 2025 04:43:46 PM Verify the display of date format Pass
    Jul 4, 2025 04:43:46 PM Verify the blood glucose value in log review section if there is no log Pass
    Jul 4, 2025 04:43:47 PM Verify the nutrient value in log review section if there is no log Pass
    Jul 4, 2025 04:43:48 PM Verify the order of date Pass
    Jul 4, 2025 04:43:50 PM Verify the blood glucose value in log review section if there is no log Pass
    Jul 4, 2025 04:43:56 PM Verify the physical activity value in log review section if there is no log Pass
    Jul 4, 2025 04:44:02 PM Verify the entries of Medication in log review section if there is no value Pass
    Jul 4, 2025 04:44:02 PM Verify the blood glucose entries in log review section if there is log Pass
    Jul 4, 2025 04:44:02 PM Verify the nutrient value in log review section if there is no log Pass
    Jul 4, 2025 04:44:05 PM Verify the nutrient value entries in log review section if there is log Pass
    Jul 4, 2025 04:44:06 PM Verify Doses Taken will display 0 doses , if no medication is displayed Pass
    Jul 4, 2025 04:44:20 PM Verify the physical activity value in log review section if there is no log Pass
    Jul 4, 2025 04:44:21 PM Verify the entries of Medication in log review section if there is no value Pass
    Jul 4, 2025 04:44:22 PM Verify the physical activity entries in log review section if there is log Pass
    Jul 4, 2025 04:44:22 PM Verify the blood glucose entries in log review section if there is log Pass
    Jul 4, 2025 04:44:23 PM Verify the medication value in log review section if there is log Pass
    Jul 4, 2025 04:44:26 PM Verify the nutrient value entries in log review section if there is log Pass
    Jul 4, 2025 04:44:27 PM Verify the physical activity entries in log review section if there is log Pass
    Jul 4, 2025 04:44:27 PM Verify the medication value in log review section if there is log Pass
    Jul 4, 2025 04:44:34 PM Verify the icon beside medical dosage Pass
    Jul 4, 2025 04:44:39 PM Verify red colour bard is displayed for doses missed on one week schedule Pass
    Jul 4, 2025 04:44:39 PM Verify the Y-axis has text "Number of Doses" Pass
    Jul 4, 2025 04:44:57 PM Verify the title "Medical dosage" Pass
    Jul 4, 2025 04:44:59 PM Verify the icon beside medical dosage Pass
    Jul 4, 2025 04:45:12 PM Verify the text colour of total calories Pass
    Jul 4, 2025 04:45:13 PM Verify the colour of Doses Taken text Pass
    Jul 4, 2025 04:45:18 PM Verify the colour of Doses Missed text Pass
    Jul 4, 2025 04:45:35 PM Verify the colour of Doses Missed text Pass
    Jul 4, 2025 04:45:35 PM verify green colour bar is displayed for doses taken on one week schedule Pass
    Jul 4, 2025 04:45:53 PM Verify the text colour of total calories Pass
    Jul 4, 2025 04:45:54 PM Verify the display of bars if there is activity log in home page Pass
    Jul 4, 2025 04:45:55 PM Verify the text colour of daily average Pass
    Jul 4, 2025 04:46:08 PM Verify last 7 days are displayed on X-axis Pass
    Jul 4, 2025 04:46:13 PM verify the text colour of peak day Pass
    Jul 4, 2025 04:46:25 PM Verify message if no medication is added Fail
    Jul 4, 2025 04:46:27 PM Verify the display of bars if there is activity log in home page Pass
    Jul 4, 2025 04:46:28 PM Verify subtext in form Fail
    Jul 4, 2025 04:46:45 PM Verify the daily average value for no activity log Pass
    Jul 4, 2025 04:47:06 PM Verify message if no medication is added Fail
    Jul 4, 2025 04:47:28 PM Verify the presence of Add Medication button Fail
    Jul 4, 2025 04:47:49 PM Verify the presence of Cancel button Fail
    Jul 4, 2025 04:49:28 PM Verify options for frequency Fail
    Jul 4, 2025 04:50:34 PM Verify dropdown for frequency Fail
    Jul 4, 2025 04:52:32 PM Verify checkbox for Take with food Fail
    Jul 4, 2025 04:52:32 PM Verify dosage input field Fail
    Jul 4, 2025 04:54:16 PM Verify Add Medication button Pass
    Jul 4, 2025 04:54:16 PM Verify scheduled time for once daily Fail
    Jul 4, 2025 04:54:43 PM Verify datepicker popup Fail
    Jul 4, 2025 04:55:18 PM Verify note field character limit Fail
    Jul 4, 2025 04:56:33 PM Remove selected medication from dropdown Fail
    Jul 4, 2025 04:56:57 PM Confirm medication removal Fail
    Jul 4, 2025 04:59:56 PM Confirm medication removal Fail
    Jul 4, 2025 05:00:18 PM Verify fields in Food Intake form Fail
    Jul 4, 2025 05:01:28 PM Verify default meal tab Pass
    Jul 4, 2025 05:01:56 PM Verify default meal tab Fail
    Jul 4, 2025 05:02:29 PM Verify options in Serving Size Fail
    Jul 4, 2025 05:02:45 PM Verify helper text under calorie field Fail
    Jul 4, 2025 05:03:01 PM Verify placeholder in calorie field Fail
    Jul 4, 2025 05:06:30 PM Verify placeholder in notes Pass
    Jul 4, 2025 05:09:06 PM Verify the presence of icon for Pre-meal Fail
    Jul 4, 2025 05:09:06 PM Verify the presence of icon for main-meal Fail
    Jul 4, 2025 05:13:25 PM Verify the time format in each main-meal Fail
    Jul 4, 2025 05:16:15 PM Verify the time in main-snack Fail
    Jul 4, 2025 05:16:22 PM Verify color change of not completed button Fail
    Jul 4, 2025 05:16:22 PM Verify the presence of ✅ Completed button Fail
    Jul 4, 2025 05:18:31 PM Verify color change of partially completed button Fail
    Jul 4, 2025 05:21:58 PM Verify each meal calorie detail on the right side Fail
    Jul 4, 2025 05:23:28 PM Verify the second option text Fail
    Jul 4, 2025 05:25:31 PM Verify meal includes description under the item name Fail
    Jul 4, 2025 05:29:22 PM Verify Personalized Exercise Plan availability Pass
    Jul 4, 2025 05:31:07 PM Verify Downloadable Meal Plan PDF availability Pass
    Jul 4, 2025 05:33:34 PM Verify position of Continue free button Fail
    Jul 4, 2025 05:40:19 PM Verify user able to go to home page Fail
    Jul 4, 2025 05:41:41 PM Verify presence of forgot password link Pass
  • @PremiumUser_LogbookPhysicalActivity 53 24
    Passed: 53 Failed: 24
    Timestamp TestName Status
    Jul 4, 2025 04:44:42 PM Verify the presence of Physical activity section Pass
    Jul 4, 2025 04:45:01 PM Verify the title of physical activity section Pass
    Jul 4, 2025 04:45:01 PM Verify the presence of icons beside title physical activity Pass
    Jul 4, 2025 04:45:05 PM Verify last 7 days are displayed on X-axis Pass
    Jul 4, 2025 04:45:07 PM Verify the alignment of statistic card "Total calories","Daily Average","Peak day" Pass
    Jul 4, 2025 04:45:12 PM Verify the text colour of total calories Pass
    Jul 4, 2025 04:45:17 PM Verify the text colour of daily average Pass
    Jul 4, 2025 04:45:19 PM verify the text colour of peak day Pass
    Jul 4, 2025 04:45:35 PM Verify Y-axis has text calories Pass
    Jul 4, 2025 04:45:35 PM Verify the presence of Physical activity section Pass
    Jul 4, 2025 04:45:37 PM Verify display of empty chart for no activity log Pass
    Jul 4, 2025 04:45:37 PM Verify the presence of Physical activity section Pass
    Jul 4, 2025 04:45:37 PM verify the total calories value for no activity log Pass
    Jul 4, 2025 04:45:40 PM Verify the title of physical activity section Pass
    Jul 4, 2025 04:45:50 PM Verify the daily average value for no activity log Pass
    Jul 4, 2025 04:45:50 PM Verify the presence of icons beside title physical activity Pass
    Jul 4, 2025 04:45:52 PM Verify the title of physical activity section Pass
    Jul 4, 2025 04:45:53 PM Verify last 7 days are displayed on X-axis Pass
    Jul 4, 2025 04:45:53 PM Verify the alignment of statistic card "Total calories","Daily Average","Peak day" Pass
    Jul 4, 2025 04:45:53 PM Verify the text colour of total calories Pass
    Jul 4, 2025 04:45:53 PM Verify the peak day value for no activity log Pass
    Jul 4, 2025 04:45:54 PM Verify the display of bars if there is activity log in home page Pass
    Jul 4, 2025 04:45:55 PM Verify the text colour of daily average Pass
    Jul 4, 2025 04:46:08 PM verify the text colour of peak day Pass
    Jul 4, 2025 04:46:08 PM Verify the presence of icons beside title physical activity Pass
    Jul 4, 2025 04:46:08 PM Verify last 7 days are displayed on X-axis Pass
    Jul 4, 2025 04:46:09 PM Verify the alignment of statistic card "Total calories","Daily Average","Peak day" Pass
    Jul 4, 2025 04:46:11 PM Verify the text colour of total calories Pass
    Jul 4, 2025 04:46:12 PM Verify the text colour of daily average Pass
    Jul 4, 2025 04:46:12 PM Verify Y-axis has text calories Pass
    Jul 4, 2025 04:46:13 PM verify the text colour of peak day Pass
    Jul 4, 2025 04:46:13 PM Verify display of empty chart for no activity log Pass
    Jul 4, 2025 04:46:21 PM Verify Y-axis has text calories Pass
    Jul 4, 2025 04:46:22 PM Verify display of empty chart for no activity log Pass
    Jul 4, 2025 04:46:25 PM verify the total calories value for no activity log Pass
    Jul 4, 2025 04:46:26 PM verify the total calories value for no activity log Pass
    Jul 4, 2025 04:46:26 PM Verify the presence of Add Medication button Pass
    Jul 4, 2025 04:46:27 PM Verify the daily average value for no activity log Pass
    Jul 4, 2025 04:46:27 PM Verify the peak day value for no activity log Pass
    Jul 4, 2025 04:46:27 PM Verify the display of bars if there is activity log in home page Pass
    Jul 4, 2025 04:46:45 PM Verify the daily average value for no activity log Pass
    Jul 4, 2025 04:46:46 PM Verify the peak day value for no activity log Pass
    Jul 4, 2025 04:46:46 PM Verify the heading in flex Fail
    Jul 4, 2025 04:46:46 PM Verify the display of bars if there is activity log in home page Pass
    Jul 4, 2025 04:47:31 PM Verify options in medication dropdown Fail
    Jul 4, 2025 04:47:38 PM Verify the presence of Close button Fail
    Jul 4, 2025 04:50:18 PM Verify dropdown in medication field Fail
    Jul 4, 2025 04:52:35 PM Verify scheduled time for three times daily Fail
    Jul 4, 2025 04:54:23 PM Remove selected medication from dropdown Fail
    Jul 4, 2025 04:54:26 PM Add medication with invalid dosage Fail
    Jul 4, 2025 04:56:42 PM Verify datepicker popup Fail
    Jul 4, 2025 05:00:03 PM Cancel medication removal Fail
    Jul 4, 2025 05:01:40 PM Verify presence of 4 tabs Fail
    Jul 4, 2025 05:01:53 PM Verify options in Serving Size Fail
    Jul 4, 2025 05:02:29 PM Verify default value in Serving Size Pass
    Jul 4, 2025 05:04:53 PM Verify default value in Date field Fail
    Jul 4, 2025 05:09:05 PM Verify the presence of meal title for main meal in snack Fail
    Jul 4, 2025 05:09:44 PM Validate the indicator for breakfast main-meal Fail
    Jul 4, 2025 05:12:58 PM Verify the presence of ⚠️ Partially Completed button Fail
    Jul 4, 2025 05:16:09 PM Verify the presence of ❌ Not Completed button Pass
    Jul 4, 2025 05:16:28 PM Verify presence of Back to Plan button Fail
    Jul 4, 2025 05:18:31 PM Verify navigation to View Full Meal Plan Fail
    Jul 4, 2025 05:21:08 PM Verify Pre meal calorie in view full plan Fail
    Jul 4, 2025 05:21:58 PM Verify the subtext in the popup Fail
    Jul 4, 2025 05:25:07 PM Verify the navigation of Physical Activity button Fail
    Jul 4, 2025 05:25:17 PM Verify nutrients list (Pre-meal portion) Fail
    Jul 4, 2025 05:28:12 PM Verify 10-Day Quick Reversal Plan availability Pass
    Jul 4, 2025 05:28:47 PM Verify Weekly Meal Plan availability Pass
    Jul 4, 2025 05:30:27 PM Verify Free Account label Pass
    Jul 4, 2025 05:30:55 PM Verify 30-Day Blood Sugar Reduction Plan Pass
    Jul 4, 2025 05:33:10 PM Verify visual separation between Free and Premium plans Fail
    Jul 4, 2025 05:33:27 PM Verify unavailable features are marked with gray X Fail
    Jul 4, 2025 05:40:18 PM Verify user able to go to home page Fail
    Jul 4, 2025 05:40:18 PM Verify terms and renewal message Pass
    Jul 4, 2025 05:41:34 PM Verify email input rejects invalid email Pass
    Jul 4, 2025 05:41:44 PM Verify presence of placeholder in password field Pass
    Jul 4, 2025 05:42:50 PM Verify email input accepts valid new email Pass
  • @PremiumUser_Exercise 160 27
    Passed: 160 Failed: 27
    Timestamp TestName Status
    Jul 4, 2025 04:27:54 PM Verify "View Full Schedule" button is displayed Pass
    Jul 4, 2025 04:27:54 PM Verify "View Full Schedule" button is displayed Pass
    Jul 4, 2025 04:28:02 PM Verify navigation to "Today's Exercise Schedule" page Pass
    Jul 4, 2025 04:28:15 PM Verify navigation to "Today's Exercise Schedule" page Pass
    Jul 4, 2025 04:28:16 PM Verify "Warm Up" tab is displayed Pass
    Jul 4, 2025 04:28:41 PM Verify "Warm Up" tab is displayed Pass
    Jul 4, 2025 04:28:41 PM Verify "Main Workout" tab is displayed Pass
    Jul 4, 2025 04:28:52 PM Verify "Cool Down" tab is displayed Pass
    Jul 4, 2025 04:28:53 PM Verify Exercise name is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:28:57 PM Verify "Main Workout" tab is displayed Pass
    Jul 4, 2025 04:29:01 PM Verify "View Full Schedule" button is displayed Pass
    Jul 4, 2025 04:29:17 PM Verify Exercise name is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:29:17 PM Verify navigation to "Today's Exercise Schedule" page Pass
    Jul 4, 2025 04:29:32 PM Verify Exercise name is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:29:34 PM Verify "Cool Down" tab is displayed Pass
    Jul 4, 2025 04:29:35 PM Verify Exercise description is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:29:36 PM Verify Exercise name is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:29:37 PM Verify Exercise name is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:29:37 PM Verify "Warm Up" tab is displayed Pass
    Jul 4, 2025 04:29:38 PM Verify Exercise description is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:29:38 PM Verify Exercise description is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:29:40 PM Verify Exercise name is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:29:40 PM Verify Exercise description is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:29:41 PM Verify Exercise description is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:29:41 PM Verify "Main Workout" tab is displayed Pass
    Jul 4, 2025 04:29:41 PM Verify duration is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:29:41 PM Verify "Cool Down" tab is displayed Pass
    Jul 4, 2025 04:29:41 PM Verify calories are displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:29:46 PM Verify Exercise name is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:29:47 PM Verify Exercise description is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:29:52 PM Verify Exercise name is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:29:58 PM Verify duration is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:30:01 PM Verify calories are displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:30:02 PM Verify intensity level is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:30:02 PM Verify duration is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:30:02 PM Verify intensity level is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:30:10 PM Verify calories are displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:30:10 PM Verify Exercise name is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:30:10 PM Verify intensity level is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:30:10 PM Verify Exercise description is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:30:13 PM Verify Exercise description is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:30:19 PM Verify duration is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:30:19 PM Verify duration is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:30:19 PM Verify calories are displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:30:20 PM Verify Exercise description is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:30:20 PM Verify calories are displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:30:20 PM Verify duration is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:30:20 PM Verify intensity level is displayed under "Main Workout" tab Fail
    Jul 4, 2025 04:30:21 PM Verify calories are displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:30:21 PM Verify duration is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:30:22 PM Verify calories are displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:30:22 PM Verify intensity level is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:30:23 PM Verify intensity level is displayed under "Warm Up" tab Pass
    Jul 4, 2025 04:30:23 PM Verify "Mark As Completed" button is displayed Pass
    Jul 4, 2025 04:30:24 PM Verify intensity level is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:30:24 PM Verify success dialog is shown after marking as completed Fail
    Jul 4, 2025 04:30:24 PM Verify button status changes to "Completed" Pass
    Jul 4, 2025 04:30:26 PM Verify "Mark As Completed" button is displayed Pass
    Jul 4, 2025 04:30:32 PM Verify duration is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:30:34 PM Verify success dialog is shown after marking as completed Pass
    Jul 4, 2025 04:30:34 PM Verify undo option is displayed after marking completed Pass
    Jul 4, 2025 04:30:34 PM Verify button status changes to "Completed" Pass
    Jul 4, 2025 04:30:35 PM Verify undo option is displayed after marking completed Pass
    Jul 4, 2025 04:30:35 PM Verify button reverts back after undo Pass
    Jul 4, 2025 04:30:57 PM Verify navigation to "View full schedule" Pass
    Jul 4, 2025 04:30:57 PM Verify calories are displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:30:57 PM Verify page title is displayed Fail
    Jul 4, 2025 04:30:58 PM Verify "Back to Home" button is visible Pass
    Jul 4, 2025 04:31:00 PM Verify "Warm Up" section is displayed Pass
    Jul 4, 2025 04:31:00 PM Verify warm-up exercise name Pass
    Jul 4, 2025 04:31:00 PM Verify intensity level is displayed under "Main Workout" tab Pass
    Jul 4, 2025 04:31:00 PM Verify warm-up exercise description Pass
    Jul 4, 2025 04:31:06 PM Verify button reverts back after undo Pass
    Jul 4, 2025 04:31:06 PM Verify navigation to "View full schedule" Pass
    Jul 4, 2025 04:31:06 PM Verify duration is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:31:07 PM Verify page title is displayed Fail
    Jul 4, 2025 04:31:07 PM Verify calories are displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:31:07 PM Verify intensity level is displayed under "Cool Down" tab Pass
    Jul 4, 2025 04:31:08 PM Verify "Back to Home" button is visible Pass
    Jul 4, 2025 04:31:08 PM Verify warm-up duration Pass
    Jul 4, 2025 04:31:08 PM Verify "Warm Up" section is displayed Pass
    Jul 4, 2025 04:31:08 PM Verify warm-up exercise name Pass
    Jul 4, 2025 04:31:10 PM Verify "Mark As Completed" button is displayed Pass
    Jul 4, 2025 04:31:10 PM Verify success dialog is shown after marking as completed Pass
    Jul 4, 2025 04:31:13 PM Verify warm-up calories Pass
    Jul 4, 2025 04:31:13 PM Verify warm-up exercise description Pass
    Jul 4, 2025 04:31:14 PM Verify warm-up duration Pass
    Jul 4, 2025 04:31:14 PM Verify button status changes to "Completed" Pass
    Jul 4, 2025 04:31:14 PM Verify warm-up intensity Pass
    Jul 4, 2025 04:31:14 PM Verify warm-up calories Pass
    Jul 4, 2025 04:31:20 PM Verify "Main Workout" section is displayed Pass
    Jul 4, 2025 04:31:21 PM Verify undo option is displayed after marking completed Pass
    Jul 4, 2025 04:31:26 PM Verify button reverts back after undo Pass
    Jul 4, 2025 04:31:30 PM Verify Main Workout exercise name Pass
    Jul 4, 2025 04:31:30 PM Verify navigation to "View full schedule" Pass
    Jul 4, 2025 04:31:32 PM Verify Main Workout exercise description Pass
    Jul 4, 2025 04:31:32 PM Verify Main Workout duration Pass
    Jul 4, 2025 04:31:33 PM Verify Main Workout calories Pass
    Jul 4, 2025 04:31:33 PM Verify page title is displayed Fail
    Jul 4, 2025 04:31:34 PM Verify warm-up intensity Pass
    Jul 4, 2025 04:31:34 PM Verify "Main Workout" section is displayed Pass
    Jul 4, 2025 04:31:35 PM Verify Main Workout intensity Pass
    Jul 4, 2025 04:31:47 PM Verify "Back to Home" button is visible Pass
    Jul 4, 2025 04:31:47 PM Verify "Warm Up" section is displayed Pass
    Jul 4, 2025 04:31:48 PM Verify Main Workout exercise name Pass
    Jul 4, 2025 04:31:48 PM Verify warm-up exercise name Pass
    Jul 4, 2025 04:31:49 PM Verify Main Workout exercise description Pass
    Jul 4, 2025 04:31:51 PM Verify warm-up exercise description Pass
    Jul 4, 2025 04:31:51 PM Verify "Cool Down" section is displayed Pass
    Jul 4, 2025 04:31:52 PM Verify Main Workout duration Pass
    Jul 4, 2025 04:31:52 PM Verify warm-up duration Pass
    Jul 4, 2025 04:31:53 PM Verify Cool Down exercise name Pass
    Jul 4, 2025 04:31:53 PM Verify Cool Down exercise description Pass
    Jul 4, 2025 04:31:55 PM Verify Main Workout calories Pass
    Jul 4, 2025 04:31:57 PM Verify Cool Down duration Pass
    Jul 4, 2025 04:31:57 PM Verify Main Workout intensity Pass
    Jul 4, 2025 04:31:57 PM Verify warm-up calories Pass
    Jul 4, 2025 04:32:01 PM Verify warm-up intensity Pass
    Jul 4, 2025 04:32:02 PM Verify Cool Down calories Pass
    Jul 4, 2025 04:32:03 PM Verify "Main Workout" section is displayed Pass
    Jul 4, 2025 04:32:03 PM Verify "Cool Down" section is displayed Pass
    Jul 4, 2025 04:32:04 PM Verify Cool Down exercise name Pass
    Jul 4, 2025 04:32:05 PM Verify Cool Down intensity Pass
    Jul 4, 2025 04:32:07 PM Verify the intensity value Pass
    Jul 4, 2025 04:32:07 PM Verify total duration is displayed Pass
    Jul 4, 2025 04:32:07 PM Verify total duration matches the sum of individual workout durations Pass
    Jul 4, 2025 04:32:09 PM Verify Cool Down exercise description Pass
    Jul 4, 2025 04:32:13 PM Verify Cool Down duration Pass
    Jul 4, 2025 04:32:17 PM Verify Main Workout exercise name Pass
    Jul 4, 2025 04:32:17 PM Verify Main Workout exercise description Pass
    Jul 4, 2025 04:32:20 PM Verify Main Workout duration Pass
    Jul 4, 2025 04:32:25 PM Verify Cool Down calories Pass
    Jul 4, 2025 04:32:27 PM Verify Cool Down intensity Pass
    Jul 4, 2025 04:32:28 PM Verify the intensity value Pass
    Jul 4, 2025 04:32:28 PM Verify total calories matches the sum of individual workout calories Pass
    Jul 4, 2025 04:32:28 PM Verify Main Workout calories Pass
    Jul 4, 2025 04:32:28 PM Verify Main Workout intensity Pass
    Jul 4, 2025 04:32:29 PM Verify "Cool Down" section is displayed Pass
    Jul 4, 2025 04:32:30 PM Verify Cool Down exercise name Pass
    Jul 4, 2025 04:32:30 PM Verify total duration is displayed Pass
    Jul 4, 2025 04:32:31 PM Verify total duration matches the sum of individual workout durations Pass
    Jul 4, 2025 04:32:42 PM Verify Cool Down exercise description Pass
    Jul 4, 2025 04:32:42 PM Verify total calories matches the sum of individual workout calories Pass
    Jul 4, 2025 04:32:44 PM Verify Cool Down duration Pass
    Jul 4, 2025 04:32:44 PM Verify Cool Down calories Pass
    Jul 4, 2025 04:32:45 PM Verify the presence of log button Pass
    Jul 4, 2025 04:32:55 PM Verify Cool Down intensity Pass
    Jul 4, 2025 04:32:55 PM Verify the intensity value Pass
    Jul 4, 2025 04:32:55 PM Verify total duration is displayed Pass
    Jul 4, 2025 04:32:59 PM Verify total duration matches the sum of individual workout durations Pass
    Jul 4, 2025 04:33:04 PM Verify the presence of emoji on top right of gender image Pass
    Jul 4, 2025 04:33:04 PM Verify total calories matches the sum of individual workout calories Pass
    Jul 4, 2025 04:33:54 PM Verify the presence of emoji on top right of gender image Fail
    Jul 4, 2025 04:34:09 PM Verify the first button text "Blood Glucose" Pass
    Jul 4, 2025 04:35:11 PM Verify the presence of "Record New Data" in the bottom Fail
    Jul 4, 2025 04:36:23 PM Verify icon for Food Intake Fail
    Jul 4, 2025 04:41:24 PM Verify the order of date Pass
    Jul 4, 2025 04:41:54 PM Verify the blood glucose entries in log review section if there is log Pass
    Jul 4, 2025 04:42:18 PM Verify log review displays last 7 days of date entries including today Pass
    Jul 4, 2025 04:42:58 PM Verify the blood glucose entries in log review section if there is log Pass
    Jul 4, 2025 04:43:48 PM Verify the order of date Pass
    Jul 4, 2025 04:44:27 PM Verify the physical activity entries in log review section if there is log Pass
    Jul 4, 2025 04:45:03 PM Verify display empty chart when no medication is scheduled Pass
    Jul 4, 2025 04:45:27 PM Verify red colour bard is displayed for doses missed on one week schedule Pass
    Jul 4, 2025 04:45:34 PM Verify the colour of Total Scheduled text Pass
    Jul 4, 2025 04:46:08 PM verify the text colour of peak day Pass
    Jul 4, 2025 04:46:09 PM Verify the alignment of statistic card "Total calories","Daily Average","Peak day" Pass
    Jul 4, 2025 04:46:49 PM Verify the default value in datepicker Fail
    Jul 4, 2025 04:46:51 PM Verify the heading in flex Fail
    Jul 4, 2025 04:50:21 PM Verify dosage input field Fail
    Jul 4, 2025 04:50:23 PM Verify dropdown in medication field Fail
    Jul 4, 2025 04:54:26 PM Verify scheduled time for three times daily Fail
    Jul 4, 2025 04:54:59 PM Verify presence of previous and next buttons in calendar Fail
    Jul 4, 2025 05:01:55 PM Verify placeholder in food name field Fail
    Jul 4, 2025 05:02:29 PM Verify dropdown for Serving Size Fail
    Jul 4, 2025 05:05:45 PM Verify date picker after popup Fail
    Jul 4, 2025 05:09:03 PM Verify meal section contains dish description in snack Fail
    Jul 4, 2025 05:09:44 PM Verify the presence of meal title for main meal in snack Fail
    Jul 4, 2025 05:11:59 PM Verify the presence of icon for main-meal Fail
    Jul 4, 2025 05:12:30 PM Validate the text "Calories" in main-meal Fail
    Jul 4, 2025 05:14:54 PM Validate the indicator for dinner main-meal Pass
    Jul 4, 2025 05:15:15 PM Verify presence of nutrition insight summary card in each meal section Fail
    Jul 4, 2025 05:16:09 PM Verify the time in main-lunch Fail
    Jul 4, 2025 05:19:44 PM Verify title in nutrition flex card Fail
    Jul 4, 2025 05:23:46 PM Verify the presence of two option buttons Fail
    Jul 4, 2025 05:25:57 PM Verify Nutrients (Pre-meal portion) Fail
    Jul 4, 2025 05:33:15 PM Verify Personalized Exercise Plan availability Fail
  • @PremiumUser_LogbookMedicalDosage 49 23
    Passed: 49 Failed: 23
    Timestamp TestName Status
    Jul 4, 2025 04:43:35 PM Verify the presence of Medical Dosage section Pass
    Jul 4, 2025 04:43:48 PM Verify the title "Medical dosage" Pass
    Jul 4, 2025 04:43:48 PM Verify the icon beside medical dosage Pass
    Jul 4, 2025 04:43:48 PM Verify the Y-axis has text "Number of Doses" Pass
    Jul 4, 2025 04:43:49 PM Verify display empty chart when no medication is scheduled Pass
    Jul 4, 2025 04:44:02 PM Verify Total scheduled will display 0 doses, if no medication is scheduled Pass
    Jul 4, 2025 04:44:06 PM Verify Doses Taken will display 0 doses , if no medication is displayed Pass
    Jul 4, 2025 04:44:23 PM Verify Doses Missed will display 0 doses, if no Medication is displayed Pass
    Jul 4, 2025 04:44:26 PM Verify the colour of Total Scheduled text Pass
    Jul 4, 2025 04:44:28 PM Verify the colour of Doses Taken text Pass
    Jul 4, 2025 04:44:29 PM Verify the presence of Medical Dosage section Pass
    Jul 4, 2025 04:44:29 PM Verify the colour of Doses Missed text Pass
    Jul 4, 2025 04:44:34 PM Verify the title "Medical dosage" Pass
    Jul 4, 2025 04:44:34 PM Verify the icon beside medical dosage Pass
    Jul 4, 2025 04:44:38 PM Verify the presence of Medical Dosage section Pass
    Jul 4, 2025 04:44:39 PM verify green colour bar is displayed for doses taken on one week schedule Pass
    Jul 4, 2025 04:44:39 PM Verify red colour bard is displayed for doses missed on one week schedule Pass
    Jul 4, 2025 04:44:39 PM Verify the Y-axis has text "Number of Doses" Pass
    Jul 4, 2025 04:44:41 PM Verify display empty chart when no medication is scheduled Pass
    Jul 4, 2025 04:44:57 PM Verify the title "Medical dosage" Pass
    Jul 4, 2025 04:44:59 PM Verify the icon beside medical dosage Pass
    Jul 4, 2025 04:45:01 PM Verify the presence of icons beside title physical activity Pass
    Jul 4, 2025 04:45:01 PM Verify Total scheduled will display 0 doses, if no medication is scheduled Pass
    Jul 4, 2025 04:45:03 PM Verify the Y-axis has text "Number of Doses" Pass
    Jul 4, 2025 04:45:03 PM Verify display empty chart when no medication is scheduled Pass
    Jul 4, 2025 04:45:04 PM Verify Total scheduled will display 0 doses, if no medication is scheduled Pass
    Jul 4, 2025 04:45:04 PM Verify Doses Taken will display 0 doses , if no medication is displayed Pass
    Jul 4, 2025 04:45:05 PM Verify Doses Taken will display 0 doses , if no medication is displayed Pass
    Jul 4, 2025 04:45:11 PM Verify Doses Missed will display 0 doses, if no Medication is displayed Pass
    Jul 4, 2025 04:45:12 PM Verify the colour of Total Scheduled text Pass
    Jul 4, 2025 04:45:13 PM Verify the colour of Doses Taken text Pass
    Jul 4, 2025 04:45:17 PM Verify Doses Missed will display 0 doses, if no Medication is displayed Pass
    Jul 4, 2025 04:45:18 PM Verify the colour of Doses Missed text Pass
    Jul 4, 2025 04:45:19 PM verify green colour bar is displayed for doses taken on one week schedule Pass
    Jul 4, 2025 04:45:27 PM Verify red colour bard is displayed for doses missed on one week schedule Pass
    Jul 4, 2025 04:45:34 PM Verify the colour of Total Scheduled text Pass
    Jul 4, 2025 04:45:35 PM Verify the colour of Doses Taken text Pass
    Jul 4, 2025 04:45:35 PM Verify the colour of Doses Missed text Pass
    Jul 4, 2025 04:45:35 PM verify green colour bar is displayed for doses taken on one week schedule Pass
    Jul 4, 2025 04:45:37 PM Verify red colour bard is displayed for doses missed on one week schedule Pass
    Jul 4, 2025 04:45:37 PM Verify display of empty chart for no activity log Pass
    Jul 4, 2025 04:45:52 PM Verify the title of physical activity section Pass
    Jul 4, 2025 04:45:53 PM Verify last 7 days are displayed on X-axis Pass
    Jul 4, 2025 04:46:12 PM Verify the presence of date picker Fail
    Jul 4, 2025 04:46:25 PM verify the total calories value for no activity log Pass
    Jul 4, 2025 04:46:27 PM Verify the peak day value for no activity log Pass
    Jul 4, 2025 04:47:13 PM Verify message if no medication is added Fail
    Jul 4, 2025 04:47:20 PM Verify the presence of Close button Fail
    Jul 4, 2025 04:47:29 PM Verify the fields in iframe Pass
    Jul 4, 2025 04:50:23 PM Verify text block for Notes Fail
    Jul 4, 2025 04:50:42 PM Verify options for frequency Fail
    Jul 4, 2025 04:52:38 PM Verify dropdown for frequency Fail
    Jul 4, 2025 04:54:16 PM Verify scheduled time for once daily Fail
    Jul 4, 2025 04:54:52 PM Remove added medication Fail
    Jul 4, 2025 04:56:26 PM Remove added medication Fail
    Jul 4, 2025 04:57:16 PM Verify user can select previous date Fail
    Jul 4, 2025 05:01:18 PM Verify fields in Food Intake form Fail
    Jul 4, 2025 05:01:56 PM Verify calculator icon in calorie field Fail
    Jul 4, 2025 05:03:50 PM Verify date picker after popup Fail
    Jul 4, 2025 05:07:55 PM Verify "None" is displayed for Pre-Meal Snack by default Pass
    Jul 4, 2025 05:09:06 PM Verify meal section contains dish description in snack Fail
    Jul 4, 2025 05:09:46 PM Validate the indicator for lunch main-meal Fail
    Jul 4, 2025 05:11:53 PM Verify the time in main-dinner Pass
    Jul 4, 2025 05:12:30 PM Verify the time in main-breakfast Fail
    Jul 4, 2025 05:13:28 PM Verify the presence of ❌ Not Completed button Fail
    Jul 4, 2025 05:15:03 PM Validate the text "Calories" in main-meal Pass
    Jul 4, 2025 05:15:56 PM Verify total calorie count from pre-meal and meal Fail
    Jul 4, 2025 05:16:24 PM Verify title in nutrition flex card Fail
    Jul 4, 2025 05:18:56 PM Verify the subtext in the popup Fail
    Jul 4, 2025 05:23:01 PM Verify nutrients list (Pre-meal portion) Fail
    Jul 4, 2025 05:26:37 PM Verify Personalized Exercise Plan availability Fail
    Jul 4, 2025 05:33:16 PM Verify title of Upgrade screen Fail
search Search
  • org.openqa.selenium.NoAlertPresentException 6
    Timestamp TestName StackTrace
    Jul 4, 2025 04:58:51 PM When the user accepts the alert
    Jul 4, 2025 04:58:51 PM When the user accepts the alert
    Jul 4, 2025 04:58:50 PM When the user declines the alert
    Jul 4, 2025 04:59:09 PM When the user declines the alert
    Jul 4, 2025 05:01:04 PM When the user accepts the alert
    Jul 4, 2025 05:01:05 PM When the user declines the alert
  • org.openqa.selenium.NoSuchSessionException 2
    Timestamp TestName StackTrace
    Jul 4, 2025 04:54:12 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • java.lang.AssertionError 101
    Timestamp TestName StackTrace
    Jul 4, 2025 04:18:18 PM Then User should see 12-hour clock indicator with AM/PM
    Jul 4, 2025 04:19:25 PM Then User should see 12-hour clock indicator with AM/PM
    Jul 4, 2025 04:19:26 PM Then User should see 12-hour clock indicator with AM/PM
    Jul 4, 2025 04:29:28 PM Then User should be redirected to the confirmation or home page with premium access enabled
    Jul 4, 2025 04:29:28 PM Then User should be redirected to the confirmation or home page with premium access enabled
    Jul 4, 2025 04:29:29 PM Then User should be redirected to the confirmation or home page with premium access enabled
    Jul 4, 2025 04:46:57 PM Then the user should see heading "Your Medications"
    Jul 4, 2025 04:47:03 PM Then the user should see heading "Today's Medications" in flex
    Jul 4, 2025 04:46:57 PM Then the user should see date picker in tracker
    Jul 4, 2025 04:47:26 PM Then the user should see subtext "Keep track of your medications and never miss a dose"
    Jul 4, 2025 04:47:47 PM Then the user should see heading "Your Medications"
    Jul 4, 2025 04:47:38 PM Then the user should see Close button in the form
    Jul 4, 2025 04:47:38 PM Then the user should see message "No medications added yet\nClick the 'Add Medication' button to get started"
    Jul 4, 2025 04:48:42 PM Then the user should see subtext "Keep track of your medications and never miss a dose"
    Jul 4, 2025 04:48:42 PM Then the user should see heading "Your Medications"
    Jul 4, 2025 04:48:42 PM Then the user should see heading "Today's Medications" in flex
    Jul 4, 2025 04:48:28 PM Then the user should see heading "Today's Medications" in flex
    Jul 4, 2025 04:48:42 PM Then the user should see date picker in tracker
    Jul 4, 2025 04:48:42 PM Then the user should see today's date as default value in datepicker
    Jul 4, 2025 04:50:17 PM Then the user should see Cancel button
    Jul 4, 2025 04:50:09 PM Then the user should see following options in medication dropdown:
    Jul 4, 2025 04:50:20 PM Then the user should see message "No medications added yet\nClick the 'Add Medication' button to get started"
    Jul 4, 2025 04:50:09 PM Then the user should see Close button in the form
    Jul 4, 2025 04:50:21 PM Then the user should see Cancel button
    Jul 4, 2025 04:50:15 PM Then the user should see Add medication button
    Jul 4, 2025 04:50:20 PM Then the user should see date picker in tracker
    Jul 4, 2025 04:50:20 PM Then the user should see message "No medications added yet\nClick the 'Add Medication' button to get started"
    Jul 4, 2025 04:50:54 PM Then the user should see dropdown for Frequency
    Jul 4, 2025 04:52:43 PM Then the user should see fields "Medication, Dosage, Frequency, Date, Take with food, Notes (optional)"
    Jul 4, 2025 04:52:42 PM Then the user should see fields "Medication, Dosage, Frequency, Date, Take with food, Notes (optional)"
    Jul 4, 2025 04:52:48 PM Then the user should see following options in medication dropdown:
    Jul 4, 2025 04:52:44 PM Then the user should see text block for Notes
    Jul 4, 2025 04:52:39 PM Then the user should see checkbox for Take with food
    Jul 4, 2025 04:52:51 PM Then the user should see input field for Dosage
    Jul 4, 2025 04:54:30 PM Then the user should see Close button in the form
    Jul 4, 2025 04:54:30 PM Then the user should see following options in frequency dropdown:
    Jul 4, 2025 04:55:34 PM Then the user should see Scheduled at 8:00 and 20:00
    Jul 4, 2025 04:56:37 PM Then the user should see Scheduled at 8:00
    Jul 4, 2025 04:56:49 PM Then the user should see Scheduled at 8:00 and 20:00
    Jul 4, 2025 04:56:49 PM Then the user should see following options in medication dropdown:
    Jul 4, 2025 04:56:49 PM Then the user should see Previous and Next buttons in the date picker
    Jul 4, 2025 04:58:46 PM Then the user should see today's date highlighted in the calendar
    Jul 4, 2025 04:58:50 PM Then the user should see Previous and Next buttons in the date picker
    Jul 4, 2025 05:01:44 PM Then User should see field for Food Name, Serving Size, Calories, Date, Notes
    Jul 4, 2025 05:01:45 PM Then User should see "Breakfast, Lunch, Dinner, Snack" tabs
    Jul 4, 2025 05:02:15 PM Then User should see "Breakfast, Lunch, Dinner, Snack" tabs
    Jul 4, 2025 05:02:15 PM Then User should see "Breakfast" tab selected by default
    Jul 4, 2025 05:02:56 PM Then User should see field for Food Name, Serving Size, Calories, Date, Notes
    Jul 4, 2025 05:03:07 PM Then User should see field for Food Name, Serving Size, Calories, Date, Notes
    Jul 4, 2025 05:04:11 PM Then User should see dropdown for serving size
    Jul 4, 2025 05:04:12 PM Then User should see dropdown for serving size
    Jul 4, 2025 05:04:10 PM Then User should see calculator icon in calorie
    Jul 4, 2025 05:04:11 PM Then User should see "Small (1/2 cup), Medium (1 cup), Large (2 cups), Custom" in foodIntake popup
    Jul 4, 2025 05:04:28 PM Then User should see calculator icon in calorie
    Jul 4, 2025 05:04:43 PM Then User should see input field for calorie
    Jul 4, 2025 05:04:44 PM Then User should see "Enter calories or click the calculator icon for automatic calculation." after popoup
    Jul 4, 2025 05:04:53 PM Then User should see text "eg.250" as placeholder
    Jul 4, 2025 05:05:00 PM Then User should see text "eg.250" as placeholder
    Jul 4, 2025 05:05:02 PM Then User should see input field for calorie
    Jul 4, 2025 05:05:00 PM Then User should see date picker
    Jul 4, 2025 05:06:26 PM Then User should see input block for notes
    Jul 4, 2025 05:06:29 PM Then User should see date picker
    Jul 4, 2025 05:06:49 PM Then User should see text "eg.250" as placeholder
    Jul 4, 2025 05:07:51 PM Then User should see "Enter calories or click the calculator icon for automatic calculation." after popoup
    Jul 4, 2025 05:08:17 PM Then User should see date picker
    Jul 4, 2025 05:08:57 PM Then User should see save food entry button
    Jul 4, 2025 05:09:41 PM Then the user should see "Pre-Meal" title under the four tabs
    Jul 4, 2025 05:18:57 PM When the user views navigation controls
    Jul 4, 2025 05:21:56 PM When the user views navigation controls
    Jul 4, 2025 05:23:24 PM Then Item description should be displayed below the item name
    Jul 4, 2025 05:23:25 PM Then Calories value should be displayed
    Jul 4, 2025 05:23:27 PM Then Each meal section should display a pre-meal item with the format "Pre-meal: "
    Jul 4, 2025 05:24:54 PM Then User should see list "carb, protein, fat, fibre"
    Jul 4, 2025 05:25:40 PM Then Calories value should be displayed
    Jul 4, 2025 05:26:23 PM Then User should redirect to Blood Glucose popup window
    Jul 4, 2025 05:26:24 PM Then User should redirect to physical activity popup window
    Jul 4, 2025 05:26:24 PM Then Item description should be displayed below the item name
    Jul 4, 2025 05:26:29 PM Then Each meal section should display a pre-meal item with the format "Pre-meal: "
    Jul 4, 2025 05:26:41 PM Then User should see list "carb, protein, fat, fibre"
    Jul 4, 2025 05:27:27 PM Then Item description should be displayed below the item name
    Jul 4, 2025 05:27:35 PM Then User should redirect to food intake popup window
    Jul 4, 2025 05:28:38 PM Then Calories value should be displayed
    Jul 4, 2025 05:28:39 PM Then User should redirect to medication popup window
    Jul 4, 2025 05:28:45 PM Then User should see list "carb, protein, fat, fibre"
    Jul 4, 2025 05:28:47 PM Then User should redirected to dashboard page
    Jul 4, 2025 05:28:57 PM Then Item description should be displayed below the item name
    Jul 4, 2025 05:30:08 PM Then User should redirect to Blood Glucose popup window
    Jul 4, 2025 05:30:51 PM Then User should redirect to food intake popup window
    Jul 4, 2025 05:30:53 PM Then User should redirect to medication popup window
    Jul 4, 2025 05:30:55 PM Then User should redirect to physical activity popup window
    Jul 4, 2025 05:30:57 PM Then User should redirected to dashboard page
    Jul 4, 2025 05:33:05 PM Then User should redirect to medication popup window
    Jul 4, 2025 05:33:06 PM Then User should redirect to physical activity popup window
    Jul 4, 2025 05:33:06 PM Then User should redirect to Blood Glucose popup window
    Jul 4, 2025 05:33:09 PM Then User should redirected to dashboard page
    Jul 4, 2025 05:33:26 PM Then User should redirect to food intake popup window
    Jul 4, 2025 05:38:17 PM Then User should be redirected to the subscription payment screen
    Jul 4, 2025 05:39:08 PM Then User should be redirected to the subscription payment screen
    Jul 4, 2025 05:40:41 PM Then User should be redirected to the home page
    Jul 4, 2025 05:41:33 PM Then User should be redirected to the home page
    Jul 4, 2025 05:41:36 PM Then User should be redirected to the home page
  • org.openqa.selenium.ElementClickInterceptedException 9
    Timestamp TestName StackTrace
    Jul 4, 2025 04:46:45 PM Then the user should see title "Diabetes Medication Tracker" after medication pop
    Jul 4, 2025 04:47:43 PM Then the user should see title "Diabetes Medication Tracker" after medication pop
    Jul 4, 2025 04:47:45 PM Then the user should see iframe
    Jul 4, 2025 04:48:48 PM Then the user should see title "Diabetes Medication Tracker" after medication pop
    Jul 4, 2025 04:50:11 PM Then the user should see iframe
    Jul 4, 2025 04:53:46 PM Then the user should see iframe
    Jul 4, 2025 04:59:17 PM Then User should see title "Food Intake Tracker" on food popup
    Jul 4, 2025 05:01:53 PM Then User should see title "Food Intake Tracker" on food popup
    Jul 4, 2025 05:01:55 PM Then User should see title "Food Intake Tracker" on food popup
  • org.openqa.selenium.WebDriverException 6
    Timestamp TestName StackTrace
    Jul 4, 2025 04:48:59 PM hooks.Hooks.quitBrowser()
    Jul 4, 2025 04:51:37 PM hooks.Hooks.quitBrowser()
    Jul 4, 2025 04:51:25 PM hooks.Hooks.quitBrowser()
    Jul 4, 2025 04:54:03 PM hooks.Hooks.quitBrowser()
    Jul 4, 2025 04:54:16 PM hooks.Hooks.quitBrowser()
    Jul 4, 2025 05:32:39 PM hooks.Hooks.quitBrowser()
  • java.lang.RuntimeException 30
    Timestamp TestName StackTrace
    Jul 4, 2025 04:54:07 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:07 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:07 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:07 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:07 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:07 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:07 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:07 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:07 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:10 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:15 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:43 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 04:54:44 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:00:48 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:00:48 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:09:02 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:09:05 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:24:35 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:14 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:29 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:43 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:44 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:44 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:44 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:46 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:54 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:54 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:55 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:57 PM stepdefinition.PremiumUser_HomePageSD.init()
    Jul 4, 2025 05:25:57 PM stepdefinition.PremiumUser_HomePageSD.init()
  • org.openqa.selenium.SessionNotCreatedException 32
    Timestamp TestName StackTrace
    Jul 4, 2025 04:52:17 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:52:32 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:53:00 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:52:17 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:52:38 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:52:50 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:52:35 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:52:35 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:53:00 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:53:00 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:52:38 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:52:32 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:52:32 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:16 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:16 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:58:14 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:58:17 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:06:32 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:06:39 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:01 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:01 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:28 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:29 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:19 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:30 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:38 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:37 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:28 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:38 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:38 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:46 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:46 PM hooks.Hooks.launchbrowser()
  • org.openqa.selenium.TimeoutException 430
    Timestamp TestName StackTrace
    Jul 4, 2025 04:14:13 PM Then User should see all the fields under Account Information section
    Jul 4, 2025 04:14:29 PM Then User should see all the fields under Account Information section
    Jul 4, 2025 04:14:51 PM Then User should see all the fields under Account Information section
    Jul 4, 2025 04:14:26 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:14:39 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:14:32 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:15:46 PM When User scrolls to the Stress Management section
    Jul 4, 2025 04:15:02 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:15:54 PM When User scrolls to the Stress Management section
    Jul 4, 2025 04:16:16 PM When User clicks breathing tab under stress management techniques
    Jul 4, 2025 04:16:19 PM Then User should see title "Present Moment Awareness"
    Jul 4, 2025 04:16:38 PM When User scrolls to the Stress Management section
    Jul 4, 2025 04:17:01 PM Then User should see title "Present Moment Awareness"
    Jul 4, 2025 04:17:03 PM When User clicks breathing tab under stress management techniques
    Jul 4, 2025 04:14:38 PM And User is in Dashboard page
    Jul 4, 2025 04:14:39 PM And User is in Dashboard page
    Jul 4, 2025 04:17:59 PM When User clicks breathing tab under stress management techniques
    Jul 4, 2025 04:17:59 PM Then User should see title "Present Moment Awareness"
    Jul 4, 2025 04:15:38 PM And User is in the Dashboard Page
    Jul 4, 2025 04:17:38 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:17:40 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:18:39 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:21:52 PM Then User should see the pre-meal calorie value
    Jul 4, 2025 04:21:54 PM Then User should see the pre-meal calorie value
    Jul 4, 2025 04:22:00 PM Then User should see the pre-meal calorie value
    Jul 4, 2025 04:22:13 PM Then User should see the pre-meal item name
    Jul 4, 2025 04:22:14 PM Then User should see the pre-meal item name
    Jul 4, 2025 04:22:14 PM Then User should see the pre-meal item name
    Jul 4, 2025 04:22:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:22:24 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:23:25 PM Then User should see the 12 o'clock
    Jul 4, 2025 04:23:54 PM Then User should see the 12 o'clock
    Jul 4, 2025 04:23:54 PM Then User should see the 12 o'clock
    Jul 4, 2025 04:21:08 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:21:09 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:21:00 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:25:10 PM Then User should see text "calories" after the calorie value in pre meal
    Jul 4, 2025 04:24:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:25:34 PM Then User should see text "calories" after the calorie value in pre meal
    Jul 4, 2025 04:22:54 PM Given User is logged into the app
    Jul 4, 2025 04:22:54 PM Given User is logged into the app
    Jul 4, 2025 04:26:40 PM Then User should see title "Today's Exercise Plan"
    Jul 4, 2025 04:23:16 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:23:25 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:23:11 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:23:13 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:27:15 PM Then User should see title "Today's Exercise Plan"
    Jul 4, 2025 04:27:21 PM Then User should see title "Today's Exercise Plan"
    Jul 4, 2025 04:24:44 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:24:41 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:24:43 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:24:42 PM Given User logs into the app
    Jul 4, 2025 04:27:31 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:25:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:25:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:25:58 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:27:00 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:27:00 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:27:00 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:27:00 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:27:44 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:31:19 PM Then User should see title "Today's Exercise Schedule"
    Jul 4, 2025 04:31:51 PM Then User should see title "Today's Exercise Schedule"
    Jul 4, 2025 04:32:00 PM Then User should see title "Today's Exercise Schedule"
    Jul 4, 2025 04:29:40 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:30:24 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:30:20 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:33:20 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:34:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:34:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:34:38 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:34:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:34:00 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:34:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:35:03 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:35:38 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:33:58 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:34:00 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:35:36 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:35:36 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:35:33 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:36:12 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:36:14 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:36:23 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:38:28 PM Then User should see title "Blood Glucose Tracker"
    Jul 4, 2025 04:37:40 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:37:55 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:37:41 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:35:12 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:35:11 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:35:10 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:35:13 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:35:11 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:35:10 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:37:37 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:35:11 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:35:17 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:37:59 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:38:54 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:38:54 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:38:00 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:37 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:34 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:34 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:50 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:34 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:32 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:59 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:40:22 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:35:28 PM Given the user is in password auth page
    Jul 4, 2025 04:39:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:17 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:39:18 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:38:43 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:38:44 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:39:12 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:39:10 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:39:13 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:39:07 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:40:00 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:39:46 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:41:44 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:43:11 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:43:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:43:18 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:43:20 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:43:22 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:43:23 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:43:45 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:43:45 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:47:46 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:47:50 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:47:48 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:48:49 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:48:48 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:48:50 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:48:49 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:48:48 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:50:21 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:50:24 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:50:30 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:50:24 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:50:25 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:50:34 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:50:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:53:11 PM Then the user should see dropdown for Frequency
    Jul 4, 2025 04:49:28 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:50:27 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:52:58 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:52:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:53:10 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:52:58 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:53:10 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:52:59 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:53:10 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:01 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:53:49 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:48 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:55:55 PM Given the user is on the home page after logging into the app
    Jul 4, 2025 04:54:07 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:55:34 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:06 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:55:48 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:56:58 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:28 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:40 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:39 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:28 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:28 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:28 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:28 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:44 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:43 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:41 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:39 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:52 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:55:07 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:55:00 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:54:59 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:55:18 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 04:58:26 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:26 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:53 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:59:09 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:59:28 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:59:42 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:30 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:35 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:36 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:38 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:41 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:43 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:44 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:46 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:46 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:49 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:49 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:58:50 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:59:27 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:01:06 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:59:27 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:59:27 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:59:27 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:01:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:02:26 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:04:17 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:04:17 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:04:27 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:04:38 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:01:55 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:01:53 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:01:53 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:01:51 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:04:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:01:56 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:01:54 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:01:40 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:01:56 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:01:56 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:01:59 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:01:56 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:04:27 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:05:19 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:05:26 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:05:20 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:04:56 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:05:01 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:25 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:49 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:58 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:05:49 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:05:50 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:05:53 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:04 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:04 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:04 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:04 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:04 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:07:58 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:07:59 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:08:35 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:03:30 PM Given User is in home page after logged into app
    Jul 4, 2025 05:08:58 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:09:38 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:09:38 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:06:42 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:09:43 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:11:12 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:08:08 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:08:35 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:11:12 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:09:39 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:11:40 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:11:47 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:09:05 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:09:05 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:09:05 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:09:06 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:09:06 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:09:03 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:09:06 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:09:06 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:09:06 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:09:06 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:12:46 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:11:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:07 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:19 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:19 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:19 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:19 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:45 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:45 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:12:27 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:12:27 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:14:36 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:14:29 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:08 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:10 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:14:37 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:13 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:13 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:13 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:14 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:14 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:14 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:14 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:13:14 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:10:17 PM Given the user is in password auth page
    Jul 4, 2025 05:14:26 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:15:39 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:16:46 PM Then the user should see title "Nutrition Insight"
    Jul 4, 2025 05:12:35 PM Given the user is in password auth page
    Jul 4, 2025 05:17:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:17:19 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:12:38 PM Given the user is in password auth page
    Jul 4, 2025 05:18:59 PM Then User should see title "Choose Your Challenge"
    Jul 4, 2025 05:16:22 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:17:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:18:10 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:18:07 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:18:10 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:18:36 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:16:22 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:16:22 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:16:22 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:18:54 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:16:21 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:16:23 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:16:18 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:16:22 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:19:04 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:16:24 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:19:14 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:19:03 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:18:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:18:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:06 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:18:40 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:13 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:18:53 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:21:52 PM Then the user should see title "Nutrition Insight"
    Jul 4, 2025 05:21:03 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:55 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:21:08 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:21:08 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:21:36 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:14 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:17 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:21:36 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:21 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:24 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:24 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:21:55 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:26 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:20:27 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:22:02 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:21:56 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:22:47 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:23:27 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:23:25 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:23:25 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:21:15 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:26:04 PM Then User should redirected to Home page
    Jul 4, 2025 05:24:54 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:53 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:40 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:23:15 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:26:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:23:29 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:23:36 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:26:24 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:26:23 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:26:24 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:26:29 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:31 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:26:41 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:27:30 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:57 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:28:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:58 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:28:47 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:57 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:28:45 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:28:39 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:27:49 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:27:50 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:27:50 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:30:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:28:18 PM Given User is in the homepage
    Jul 4, 2025 05:30:55 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:32:53 PM Then User should redirected to Home page
    Jul 4, 2025 05:30:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:30:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:30:17 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:31:40 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:33:09 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:33:07 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:32:03 PM Given User is in the homepage
    Jul 4, 2025 05:32:03 PM Given User is in the homepage
    Jul 4, 2025 05:33:04 PM Given User is in the homepage
    Jul 4, 2025 05:33:29 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:15 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:16 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:32 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:10 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:01 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:03 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:27 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:04 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:15 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:02 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:34 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:08 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:25 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:31 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:33:01 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:35:06 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:35:06 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:36:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:36:28 PM Given User is in the homepage
    Jul 4, 2025 05:37:11 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:13 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:13 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:13 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:13 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:13 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:13 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:14 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:15 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:17 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:37:17 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:39:28 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:40:19 PM hooks.Hooks.launchbrowser()
    Jul 4, 2025 05:44:01 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • java.lang.NullPointerException 30
    Timestamp TestName StackTrace
    Jul 4, 2025 04:54:08 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:07 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:07 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:07 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:07 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:12 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:12 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:12 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:12 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:07 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:16 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:43 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 04:54:44 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:00:48 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:00:48 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:09:02 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:09:05 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:24:35 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:14 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:30 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:43 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:44 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:44 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:44 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:46 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:55 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:55 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:55 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
    Jul 4, 2025 05:25:57 PM hooks.Hooks.tearDown(io.cucumber.java.Scenario)
  • org.openqa.selenium.NoSuchElementException 134
    Timestamp TestName StackTrace
    Jul 4, 2025 04:14:32 PM When User clicks the dropdown of Exercise Routine Level
    Jul 4, 2025 04:15:44 PM When User clicks the dropdown of Exercise Routine Level
    Jul 4, 2025 04:20:44 PM Then User should see a caret toggle icon next to the "Today's Meal Plan" title
    Jul 4, 2025 04:21:01 PM Then User should see a caret toggle icon next to the "Today's Meal Plan" title
    Jul 4, 2025 04:21:21 PM Then User should see a caret toggle icon next to the "Today's Meal Plan" title
    Jul 4, 2025 04:24:25 PM Then User should see a caret toggle icon next to the "Today's Meal Plan" title
    Jul 4, 2025 04:24:38 PM Then User should see a caret toggle icon next to the "Today's Meal Plan" title
    Jul 4, 2025 04:24:39 PM Then User should see a caret toggle icon next to the "Today's Meal Plan" title
    Jul 4, 2025 04:27:54 PM When User clicks view full schedule button after reaching exercise section
    Jul 4, 2025 04:28:12 PM When User clicks view full schedule button after reaching exercise section
    Jul 4, 2025 04:28:55 PM When User clicks view full schedule button after reaching exercise section
    Jul 4, 2025 04:28:50 PM When User enters an invalid card number
    Jul 4, 2025 04:28:47 PM When User enters an invalid card number
    Jul 4, 2025 04:28:47 PM When User enters an expired card
    Jul 4, 2025 04:29:29 PM When User enters an expired card
    Jul 4, 2025 04:29:30 PM When User enters an expired card
    Jul 4, 2025 04:29:38 PM When User enters an invalid card number
    Jul 4, 2025 04:33:18 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:33:19 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:33:54 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:33:56 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:33:56 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:33:56 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:33:55 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:34:32 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:34:48 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:35:31 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:35:31 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:35:32 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:35:31 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:36:10 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:36:11 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:36:20 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:37:32 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:37:35 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:37:37 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:37:54 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:37:56 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:37:58 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:37:59 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:38:50 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:38:50 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:39:28 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:39:29 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:39:29 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:39:29 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:39:35 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:39:47 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:39:57 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:40:19 PM When the user clicks sign in after entering password
    Jul 4, 2025 04:50:19 PM Then the user should see dropdown for Medication
    Jul 4, 2025 04:52:43 PM Then the user should see dropdown for Medication
    Jul 4, 2025 04:52:43 PM Then the user should see dropdown for Medication
    Jul 4, 2025 04:55:34 PM When the user enters invalid dosage and clicks Add Medication
    Jul 4, 2025 04:56:10 PM When the user leaves dosage field blank and clicks Add Medication
    Jul 4, 2025 04:56:48 PM When the user fills out the medication form with valid data
    Jul 4, 2025 04:58:24 PM Then the user should see remove icon "X"
    Jul 4, 2025 04:58:13 PM When the user clicks the date field
    Jul 4, 2025 04:58:41 PM When the user clicks Remove button for an added medication
    Jul 4, 2025 04:59:09 PM When the user clicks Mark as Taken button
    Jul 4, 2025 04:59:32 PM When the user selects previous date
    Jul 4, 2025 05:01:05 PM When the user clicks Mark as Taken button
    Jul 4, 2025 05:01:45 PM When the user clicks Mark as Taken button
    Jul 4, 2025 05:06:12 PM Then User should see toadys date
    Jul 4, 2025 05:07:48 PM Then User should see toadys date
    Jul 4, 2025 05:07:48 PM Then User should see toadys date
    Jul 4, 2025 05:08:53 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:09:29 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:09:31 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:09:32 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:09:32 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:11:03 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:11:03 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:11:16 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:11:34 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:11:37 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:11:37 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:11:38 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:11:39 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:11:45 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:11:47 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:12:00 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:12:43 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:12:43 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:13:03 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:13:15 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:13:15 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:13:16 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:13:15 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:13:43 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:13:43 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:13:56 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:14:17 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:14:23 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:14:25 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:14:35 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:14:35 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:15:28 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:15:32 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:15:58 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:16:06 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:16:14 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:16:15 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:16:51 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:16:56 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:17:13 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:17:14 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:17:52 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:17:56 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:18:01 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:18:02 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:18:02 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:18:33 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:18:54 PM Then User should get pop window
    Jul 4, 2025 05:18:54 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:19:01 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:19:03 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:20:03 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:20:04 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:20:52 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:20:52 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:21:06 PM Then User should see two options for challenge option
    Jul 4, 2025 05:21:08 PM Then User should see sub text on challenge popup "Select a program that best fits your health goals"
    Jul 4, 2025 05:21:32 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:21:32 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:21:54 PM Then User should see "10-Day Challenge Postprandial Blood Glucose Reduction" as first option
    Jul 4, 2025 05:22:35 PM Then User should see "4-Week Program Blood Sugar Reduction Plan" as first option
    Jul 4, 2025 05:22:37 PM Then User should get pop window
    Jul 4, 2025 05:23:50 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:23:55 PM Then User should see sub text on challenge popup "Select a program that best fits your health goals"
    Jul 4, 2025 05:24:32 PM When the user clicks sign in after entering password
    Jul 4, 2025 05:25:49 PM Then User should see "4-Week Program Blood Sugar Reduction Plan" as first option
    Jul 4, 2025 05:25:52 PM Then Preparation instructions displayed if available, if not then "N/A"
    Jul 4, 2025 05:31:40 PM Then Preparation instructions displayed if available, if not then "N/A"
Dashboard
Features
81
Scenarios
1,218
Steps
4,719
Start
Jul 4, 2025 04:13:17 PM
End
Jul 4, 2025 05:47:02 PM
Time Taken
01 33 44.540
Categories

 

Name Passed Failed Skipped Passed %
@physicalActity 20 56 0 26.316%
@FoodIntake 0 3 0 0%
@PremiumUser_LogbookBloodGlucoseTracker 52 42 0 55.319%
@PremiumUser_LogbookLogReview 102 32 0 76.119%
@PremiumUser_LogbookPhysicalActivity 53 24 0 68.831%
@PremiumUser_Exercise 160 27 0 85.561%
@PremiumUser_LogbookMedicalDosage 49 23 0 68.056%